-
Notifications
You must be signed in to change notification settings - Fork 91
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
feat(general): Add schema for success metrics #593
Conversation
/// Example: malformed/unparseable debug information files. | ||
/// | ||
/// This metric is measured in Sentry and should be reported in all processing tasks. | ||
#[metastructure(field = "error.processing")] |
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.
To go in line with the others, should we rather call this num.processing.errored
and num.processing.failed
?
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.
it's a boolean though. maybe flag
, bool
or even is.processing.failed
?
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.
Oh, right. All of these sound good 👍
Do we want to count errors maybe? I don't see much value in it, so the flag should be enough.
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 have an implementation of this linked in the PR description and I'd say it's too hard and may be misleading as we don't really know how much soft errors are swallowed by fatal errors.
This serves only documentation purposes. Adds metrics for errors and failures in the processing pipeline.
Used in getsentry/sentry#19068