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
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions relay-general/src/protocol/metrics.rs
Original file line number Diff line number Diff line change
Expand Up @@ -111,6 +111,24 @@ pub struct Metrics {
/// This metric is measured in Sentry and reported in the javascript processing task.
#[metastructure(field = "ms.processing.sourcemaps")]
pub ms_processing_sourcemaps: Annotated<u64>,

/// Whether there has been a processing error that likely impacts the usefulness of an event.
///
/// Example: malformed/unparseable debug information files.
///
/// This metric is measured in Sentry and should be reported in all processing tasks.
#[metastructure(field = "flag.processing.error")]
pub flag_processing_error: Annotated<bool>,

/// Whether there has been a processing error that almost certainly renders the event
/// unusuable.
///
/// Example: Minidump could not be parsed, but we do not drop the event as it may still contain
/// context data and attachments, and we already billed the user anyway.
///
/// This metric is measured in Sentry and should be reported in all processing tasks.
#[metastructure(field = "flag.processing.fatal")]
pub flag_processing_fatal: Annotated<bool>,
}

// Do not process Metrics
Expand Down