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.

Sign up for GitHub

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

Jump to bottom

Include tracebacks as first-class in error monitoring #54

Closed
Tracked by #61
emmatyping opened this issue Oct 14, 2022 · 0 comments · Fixed by getsentry/self-hosted#1775
Closed
Tracked by #61

Include tracebacks as first-class in error monitoring #54

emmatyping opened this issue Oct 14, 2022 · 0 comments · Fixed by getsentry/self-hosted#1775

Comments

@emmatyping
Copy link
Contributor

Tracebacks are the central part of Sentry! We should use them.
This was referenced Oct 22, 2022
Merged
Closed
emmatyping added a commit to getsentry/self-hosted that referenced this issue Oct 26, 2022
@emmatyping
Upload end of log as breadcrumbs, use exceptions and stacktrace (#1775)
3a07ff4 
In this PR, we change the send-event function to write out more information into the envelope we send via sentry-cli, particularly adding breadcrumbs with the end of the log and giving the stack trace in a format Sentry self-hosted can understand.

Fixes getsentry/team-ospo#54 and getsentry/team-ospo#53
Example issue with this formatting: https://self-hosted.getsentry.net/organizations/self-hosted/issues/227/?query=is%3Aunresolved
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Upload end of log as breadcrumbs, use exceptions and stacktrace getsentry/self-hosted
1 participant
@emmatyping