Skip to content
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

Merged
merged 3 commits into from
May 29, 2020
Merged

Conversation

untitaker
Copy link
Member

@untitaker untitaker commented May 28, 2020

This serves only documentation purposes. Adds metrics for errors and failures in the processing pipeline.

Used in getsentry/sentry#19068

@untitaker untitaker requested a review from a team May 28, 2020 15:43
@jan-auer jan-auer requested a review from mitsuhiko May 28, 2020 17:57
/// Example: malformed/unparseable debug information files.
///
/// This metric is measured in Sentry and should be reported in all processing tasks.
#[metastructure(field = "error.processing")]
Copy link
Member

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?

Copy link
Member Author

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?

Copy link
Member

@jan-auer jan-auer May 28, 2020

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.

Copy link
Member Author

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.

@jan-auer jan-auer changed the title ref: Add schema for success metrics feat(general): Add schema for success metrics May 29, 2020
@jan-auer jan-auer merged commit 9667c18 into master May 29, 2020
@jan-auer jan-auer deleted the ref/success-metrics branch May 29, 2020 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants