Sentry tells you when the application is throwing errors. Malveon ingests those events so they become part of incident context.
Errors become incident signal
Sentry sends error events to Malveon over a webhook, verified with an HMAC signature (a sentry-hook-signature header) before processing. Verified events are recorded as incidents and feed the Malviont incident-triage correlation, so the exception count is surfaced alongside the deploy and the metric spike that accompanied it.
Not yet: health confidence
For honesty: the Malvedeck confidence rubric has a reserved Sentry error-spike criterion that is not yet wired (it always scores zero today). So Sentry contributes to incident triage now, but does not yet influence Malvedeck confidence. See the Confidence Scoring page.