feat(autofix): Add pr event tags to langfuse traces #823
Conversation
There was a problem hiding this comment.
LGTM code-wise (though minor merge conflict needs to be fixed).
Though this won't actually do anything without changes in Sentry, right? Is there a PR for that?
I'm also not fully clear on how this endpoint can be used in an Autofix run besides PR creation. I would imagine a lot of the PR actions this endpoint says it can log will happen long after the Autofix run is completed and the Sentry web app closed.
How will Sentry know if a user closed or merged a PR created by Autofix? What if the user merges the PR while the Sentry web app is closed? Does it call this endpoint when the user re-opens the issue and the GitHub status is updated? Are we using webhooks (#454)?
(this is more about Sentry than Seer, but I'm wondering how this endpoint can be used as intended)
Also some questions on other PR events and related data we want to track below.
| action_tag_map = {"opened": "pr:opened", "closed": "pr:closed", "merged": "pr:merged"} | ||
|
|
There was a problem hiding this comment.
Do we want to support other actions as well? Like commenting, editing, approving, requesting changes, etc.?
There was a problem hiding this comment.
Are we differentiating between who takes an action? Autofix agent vs. human?
Logs PR events as langfuse trace tags for visibility. Will need to have sentry call this endpoint.
TODO: Log to sentry LLM monitoring too
Tested locally w/ dev version of langfuse.