Sentry-Compatible SDKs

Use this setup guide when your application already uses a Sentry SDK, or when you need Sentry-compatible features such as exception envelopes, breadcrumbs, session replay, and source-map upload workflows. For new vendor-neutral logs, traces, and metrics, start with OpenTelemetry.

Sentry SDK compatibility

Moneat accepts Sentry protocol envelopes. You can use any official Sentry SDK by pointing its DSN to your Moneat service.

90+ platforms supported

Any platform with a Sentry SDK works with Moneat. This includes all major languages, frameworks, and mobile platforms.

Finding your DSN

Your DSN (Data Source Name) is available in your service settings under the Sentry-compatible source. The DSN format is:

https://<public_key>@api.moneat.io/api/<project_id>

Platform-specific setup

Select your platform below to see the setup steps. Replace YOUR_DSN_HERE with your service DSN from the dashboard.

1
Install the package
Install the Sentry React SDK.
```
npm install @sentry/react
```

Initialize in entry point

Initialize Sentry before rendering your React app.

import * as Sentry from "@sentry/react";

Sentry.init({
  dsn: "YOUR_DSN_HERE",
  integrations: [
    Sentry.browserTracingIntegration(),
    Sentry.replayIntegration(),
  ],
  tracesSampleRate: 1.0,
  replaysSessionSampleRate: 0.1,
  replaysOnErrorSampleRate: 1.0,
});

Verify installation

Capture a test message.

Sentry.captureMessage("Moneat test event from React");

Other platforms

For platforms not listed above, refer to the official Sentry SDK documentation and replace the DSN with your Moneat DSN.

Common options

These SDK options work across Sentry-compatible SDKs:

dsn - Your Moneat service DSN
release - Your app version for release tracking
environment - Deployment environment such as production or staging
tracesSampleRate - Percentage of transactions to capture
beforeSend - Callback to modify or filter events before sending
sampleRate - Percentage of error events to capture

Start with full sampling

Set tracesSampleRate: 1.0 during development. In production, lower it to reduce data volume and costs, for example 0.1 for 10% transaction sampling.

Coming from another vendor

If the instrumentation you are replacing is highlight.io rather than a Sentry SDK, the package and call-site changes are listed page by page in Migrate from Highlight.io.