Muon + Sentry
Connect Sentry to Muon to correlate error issues with product metric changes — so an error spike and a conversion drop stop living in separate tools. Muon does not replace Sentry for deep debugging.
What does the Muon Sentry integration do?
The Sentry integration brings issues and events onto the Muon timeline, and Muon correlates error spikes with conversion changes — so you can see when a broken build actually cost you signups.
Muon is not a Sentry replacement. Use Sentry for deep debugging, stack traces and source maps; use Muon to connect those errors to product impact. Statistics detect the metric change first; the error spike is offered as a likely related signal.
Issue and event signals, on the timeline.
Muon reads enough to place an error spike in time and link back to the issue — not to become your debugger.
Issues and events
New and reopened issues, and event volume, land on the Muon timeline as the error signal rises or falls.
Accurate timestamps
First-seen and spike times let Muon line an error surge up against the moment a product metric started to move.
Related metadata
Project, environment, release, error type and event counts — the context that tells you which failure this actually was.
Links back to source
Each timeline event links straight back to the Sentry issue, so you jump to Sentry for the stack trace and source maps.
From "errors are up" to "errors are costing conversions."
Once Sentry issues share a timeline with your product metrics, the product question gets an answer.
Timeline events
Error spikes appear as first-class markers alongside conversions, releases and browser health signals.
Correlation with product metrics
Muon scores whether an error spike lines up in time with a conversion change — surfaced with confidence and impact, not certainty.
Investigation context
When you open a Finding, the nearby Sentry issues are already attached, so you know which failure to click into.
Insight summaries
Muon Pro can write a plain-language summary naming the likely-related error spike, then hand you off to Sentry to debug it.
What a Sentry-correlated Finding looks like.
Correlation is not causation — Muon surfaces the error spike as a related signal with confidence and impact. Use Sentry for the deep debugging.
Five steps to Sentry on your timeline.
The official Sentry integration is part of Muon Pro. On Community, the same signals can flow in through the open connector API.
Open Settings → Integrations
Head to the Integrations panel in your Muon project settings.
Choose Sentry
Select Sentry from the official integration catalogue.
Authorize access
Grant read access to issues and events via a Sentry auth token or integration install.
Select projects and environments
Map the Sentry projects and environments to the Muon projects where their events belong.
Start receiving timeline events
Issues and error spikes flow onto the timeline and become available for Findings.
Questions, answered directly.
What does the Muon Sentry integration do?
Does Muon replace Sentry?
Is the Sentry integration free?
See when errors actually cost you conversions.
Official integrations like Sentry are part of Muon Pro — and a community connector API lets any team push the same events on Community.