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

Two tiny tweaks for Sentry #91

Merged
merged 2 commits into from
Nov 21, 2018
Merged

Two tiny tweaks for Sentry #91

merged 2 commits into from
Nov 21, 2018

Conversation

philbooth
Copy link
Contributor

@philbooth philbooth commented Nov 21, 2018

Fixes #90.

These are both things I had to fix recently in fxa-email-service, I presume we want to do the same here.

  • In b2935f5, I stop capturing every error in Sentry because it's too noisy. Currently the only 500 errors we return are from the db error module, so I moved the capture into there.

  • In 9d99c01, I include debug symbols in the release builds so that Sentry can include line numbers in stack traces.

@bbangert @pjenvey r?

@philbooth philbooth self-assigned this Nov 21, 2018
Cargo.toml Outdated
@@ -7,6 +7,10 @@ authors = [
"Phil Jenvey <[email protected]>",
]

[profile.release]
# Enables line numbers in Sentry
debug = true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took me a while to track this down, we came across it for autopush-rs. There's also a not well documented debug value of either 1 (or 2, but true is the equivalent of 2). This value's passed along to rustc -C debuginfo:

    -C            debuginfo=val -- debug info emission level, 0 = no debug info, 1 = line tables only, 2 = full debug info with variable and type information

debug = 1 sounds ideal for release builds, just producing the line tables

There's been some reports of slowdowns with full release = 2 which may or may not be fixed:

rust-lang/rust#49227

debug = 1 should at the very least reduce the binary size

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.

Don't send 4xx errors to Sentry
2 participants