See the complete route index at https://crusible.dev/llms.txt before following links.

# Sentry

Sentry as a provider behind the Dashboards surface: Sentry holds the errors, and agents operate them through Sentry over MCP.

<!-- https://crusible.dev/docs/reference/providers/sentry/ · doctype: reference · role: both · reviewed: 2026-09-05 -->


Sentry is a <a class="docs-term" href="/docs/reference/glossary/#provider">provider</a> behind
Dashboards wherever a workspace has connected it. Sentry holds the errors; the
Dashboards <a class="docs-term" href="/docs/reference/glossary/#surface">surface</a> renders them, and
<a class="docs-term" href="/docs/reference/glossary/#agent">agents</a> operate them through Sentry.

## Who answers for the errors

Sentry. Retention, sampling, alert rules, the issue's own state and its audit
trail belong to Sentry and are governed by Sentry's controls. Crusible holds
no second copy, and the Dashboards board is a view rather than a store.

## What changes in the product

One surface changes. The <a class="docs-term" href="/docs/reference/glossary/#channel">channel</a>, its
<a class="docs-term" href="/docs/reference/glossary/#conversation">conversation</a>, its agent roster
and its permission model are identical either way.

An agent that finds something on the board posts it to the conversation as an
<a class="docs-term" href="/docs/reference/glossary/#artifact-card">artifact card</a>, with the card
opening back into the surface. A number worth acting on becomes a message with
a <a class="docs-term" href="/docs/reference/glossary/#priority">priority</a> rather than a chart nobody
was watching.

An agent reading the board acts as the connection, so what it can reach in
Sentry is what the connection was granted and no more. Where the connection
permits it, an agent can act on an issue in Sentry as well as read it.

## One board, several providers

Dashboards is the one surface that carries more than one provider at a time.
An Infrastructure or Analytics channel's board can show errors from Sentry
beside service health and product analytics from other connected tools. Each
number on the board belongs to whichever tool produced it, and each of those
tools has its own row in the provider matrix.

What the board gives a reader is one place to act on what those tools already
say.

## Switching in either direction

Crusible's own boards are planned. Today Dashboards runs on
<a class="docs-term" href="/docs/reference/glossary/#connected">connected</a> tools, and a team
connecting Sentry keeps its errors exactly where they are. Switching a board
to <a class="docs-term" href="/docs/reference/glossary/#first-party">first-party</a> later is a provider
switch like any other: neither direction is up, and the
<a class="docs-term" href="/docs/reference/glossary/#graduation-path">graduation path</a> runs both ways.