Error Monitoring

Capture, group, and analyze errors from connected telemetry sources.

How it works

Moneat turns error telemetry into issues your team can triage. When an error arrives, Moneat normalizes the payload, extracts exception and runtime context, generates a fingerprint, and stores the event history for analysis.

Error monitoring is source-neutral in the dashboard. Source-specific details only matter when you are configuring ingestion or troubleshooting a payload.

Ingestion sources

Source	Error data Moneat can use
Sentry-compatible SDKs	Exception events, breadcrumbs, tags, users, request data, releases, and replays
OpenTelemetry	Span status, exception events, exception attributes, and related logs
Datadog-compatible intake	APM and log error context from compatible agents

Sentry-compatible SDKs are currently the richest source for full exception events and client replay correlation. OpenTelemetry and Datadog-compatible telemetry still contribute error context to traces, logs, service health, and related issue workflows as supported by the incoming signal.

Sentry-compatible envelope endpoint

When you use a Sentry-compatible SDK, the SDK sends events to the envelope endpoint automatically:

HTTP

POST /api/{projectId}/envelope/
Content-Type: application/x-sentry-envelope
X-Sentry-Auth: Sentry sentry_key=<public_key>,sentry_version=7

The endpoint supports gzip compression. Events are processed asynchronously and typically appear in the dashboard within seconds.

Event data

Error events can include:

Exception details - Type, message, and stack trace
Breadcrumbs - Trail of events leading up to the error
Tags - Key-value pairs for filtering, such as environment and release
User context - User ID, email, and IP address when provided
Device/OS info - Platform, browser, and OS version
Request data - URL, method, and request metadata for web applications
Custom context - Additional fields attached by the source SDK or exporter

Error grouping

Automatic fingerprinting

Moneat groups similar errors into issues using fingerprinting. The fingerprint is generated from a combination of:

Exception type and message
Top 3 stack trace frames
Platform identifier

This means repeated occurrences of the same error are grouped into one issue, making it easier to understand scope and impact.

Custom fingerprinting

Sentry-compatible SDKs can override default grouping with a custom fingerprint:

JavaScript

Sentry.captureException(error, {
  fingerprint: ["custom-group-key"],
});

Usage & rate limiting

Moneat meters ingestion by plan and billable usage rather than by source-specific event quotas. If an organization reaches a configured budget cap or ingestion limit, Moneat can reject or drop new events to protect the account.

Usage tracking

Monitor usage, included capacity, overages, and budgets under Billing & Plans.

Supported platforms

Any platform that can emit OpenTelemetry errors, Sentry-compatible envelopes, or compatible agent telemetry can contribute error context to Moneat.

For full exception capture through Sentry-compatible SDKs, popular platforms include JavaScript, TypeScript, Python, Java, Kotlin, Swift, Go, Ruby, PHP, .NET, Rust, Elixir, React, Vue, Angular, Next.js, Django, Flask, Spring, Android, iOS, React Native, Flutter, and Node.js.