-
Notifications
You must be signed in to change notification settings - Fork 2
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: /usr/bin/script wrapper to send full tty output to sentry #124
base: main
Are you sure you want to change the base?
Conversation
devenv/main.py
Outdated
if rc == 0: | ||
return rc | ||
|
||
# i'd love to be able to send a full event in the child then |
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 wonder if we can do something something trace id and have both exist? and just link them after the fact?
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.
ahhh that might work, i'm thinking we start a transaction in the parent and start a span for the child process then only transaction.finish() if an error happens in the child
not sure what the transaction would look like in sentry ui (like, can we easily see the child error event) but gonna give it a go
) This reverts commit 09cdabf. Wasn't roll forwardable anyways since `make instlal-py-dev` goes through do.sh, which I plan on removing. Functionality will be preserved as part of getsentry/devenv#124 where span durations would work.
closes #91
devenv now executes itself with script to tee the full tty output into a log file, which is then uploaded to sentry as an attachent to an event in the case of an unsuccessful exit.
I wasn't able to find a way to upload an attachment to an event after-the-fact though, so we're missing out on any detailed stacktrace that occured in devenv.
Events are grouped under user@host so we can easily see someone's issue.
TODO: fetch the event title (based on returned event id) because these attachment names are not that helpful.
Probably as a followup though. https://docs.sentry.io/api/events/retrieve-an-event-for-a-project/