feat(sentry): wrap runs into Sentry transactions - #580
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request replaces the jira_issue_context context manager with start_transaction in ymir/agents/observability.py to integrate Sentry transaction tracking across various agents (backport, preliminary testing, rebase, rebuild, and triage). The feedback recommends using sentry_sdk.start_transaction as a context manager to ensure transactions are properly finished and errors are reported even if exceptions occur, while also safely handling cases where the workflow parameter is None.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
• Should provide better UX with Sentry events • Also it should be possible to query Sentry logs and events by the Jira ticket Signed-off-by: Matej Focko <mfocko@packit.dev>
It appears that the process that loads the agent as a module results in a logger name consisting of ‹__main__›, therefore switch to the filename instead of the name of the module. Signed-off-by: Matej Focko <mfocko@packit.dev>
ef0451b to
1409a6d
Compare
2 participants
• Should provide better UX with Sentry events
• Also it should be possible to query Sentry logs and events by the Jira
ticket