I haven't used Sentry's obserability portions, but the error capture has very strong deduplication built into it, and can optionally integrate with your SCM, CI, and issue tracker, if one wishes. Thus, the flow can go like:

- error happens, can be attributed to release 1.2.3

- every subsequent time that error happens to a different user, it can track who was affected by it, without opening a new error report

- your project can opt-in to accepting end-user feedback on error: "please tell us what you were doing when this exploded, or feel free to rant and rave, we read them all"

- it knows from the stack trace that the error is in src/kaboom/onoz.py line 55

- onoz.py:55 was last changed by [email protected] last week, in PR #666

- sentry can comment upon said PR to advise the reviewers of the bad outcome

- sentry can create a Jira with the relevant details

- [email protected] can mark the bug as "fixed in the next release", which will cause sentry to suppress chirping about it until it sees a release 1.2.4

- if it happens again it will re-open the prior error report, marking it as a regression

Unless you know something I don't, Grafana does *ABSOLUTELY NONE* of that