Arthur MCPArthur MCP
Dashboard
How it worksFeaturesDocsEarly accessGitHubDashboard

How to Connect an Error Tracking Provider

Wire Arthur's backend into the error-monitoring provider your team already uses, so runtime failures show up on a dashboard instead of only in server logs.

Steps

  1. Go to Error Tracking and add a new provider.

    Open the configured platform-wide Sentry integration

  2. Enter the connection details your provider requires (for example, a DSN).

    Frame the protected Sentry DSN and connected state

    Demonstrate the environment label used to separate Sentry events without saving it

    Demonstrate the project name sent with error events without saving it

    Show where the saved DSN connection can be verified

  3. Save.

    Restore the fixture's original environment before closing the page

  4. Trigger a test failure, or wait for a real one, and check your provider's dashboard.

    Restore the fixture's original project name without persisting any temporary edit

Confirm it worked

The failure appears on your provider's dashboard with useful context — route, error source, status code.

Good to know

  • Request bodies, cookies, authorization headers, API keys, connection strings, and secret values are never forwarded — only the failure and its context.
  • Error Tracking is about unexpected runtime failures. Deliberate changes made by people are tracked separately in Audit Logs.

Related

Tutorial video