-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Monitoring] Adding instrumentation for bugs opened/closed #4322
Conversation
@@ -261,6 +261,7 @@ def _file_issue(testcase, issue_tracker, throttler): | |||
|
|||
if throttler.should_throttle(testcase): | |||
_add_triage_message(testcase, 'Skipping filing as it is throttled.') | |||
monitoring_metrics.ISSUE_FILING_THROTTLED.increment({'fuzzer_name': testcase.fuzzer_name}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One alternative would be to have a single ISSUE_FILLING metric, and a label to indicate throttled/success/failure, to define less metric types.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it might be more convenient to have a single issue_filing metric with 3 possible values (success, failure, throttling). Same for ISSUE_CLOSING which can have two values(success, failure)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will send a followup one to simplify this.
…by other entrypoints
ad06754
to
b2be3ef
Compare
Motivation
Opening and closing bugs is the last step in the clusterfuzz user journey, and we currently do not have that instrumentation. This PR:
The only relevant label for these metrics is the fuzzer name.
For bug filing, we measure how many attempts:
For bug closing, we measure how many attempts:
Part of #4271