moneat.io

Performance Monitoring

Moneat ingests distributed traces and spans from OpenTelemetry exporters, Sentry-compatible SDKs, and Datadog-compatible agents, then shows them in one Performance view.

OpenTelemetry traces

Send traces to Moneat using any OpenTelemetry SDK or Collector:

POST __MONEAT_BACKEND_URL__/v1/traces
POST __MONEAT_BACKEND_URL__/v1/traces/otlp

Authenticate with an OTLP API key passed as a Bearer token in the Authorization header. Create OTLP API keys from Settings -> API Keys -> OpenTelemetry.

OTLP spans are parsed, stored in ClickHouse, and shown in the same traces view as other sources. Moneat extracts error information from OTLP span status and exception events.

OTLP API keys

OTLP API keys are organization-level and shared across logs, traces, metrics, and OTLP feedback.

OpenTelemetry metrics

Moneat supports OTLP metric ingestion for gauges, sums, and histograms:

POST __MONEAT_BACKEND_URL__/v1/metrics
POST __MONEAT_BACKEND_URL__/v1/metrics/otlp

Metrics are stored in ClickHouse and available for querying through custom dashboards.

Sentry-compatible transactions

When using a Sentry-compatible SDK with tracesSampleRate configured, the SDK sends transaction and span data to Moneat through the envelope endpoint. Transactions represent top-level operations, such as an HTTP request or page load, and contain child spans for individual units of work.

The performance overview shows:

  • Transaction groups with p50, p75, and p95 latencies
  • Throughput
  • Failure rate and Apdex score
  • Slowest transactions over time

Click a transaction to see its span waterfall and related errors.

Datadog-compatible APM traces

If you run a compatible Datadog Agent, APM traces are ingested through the Datadog trace endpoints. Spans are stored with service, resource, and operation metadata.

The traces view shows:

  • Trace list with service and duration filters
  • Trace detail with a span waterfall
  • Resource-level aggregate stats, including hits, errors, and latency percentiles

Service map

The service map is built from APM spans across all telemetry sources. It shows services as nodes and inter-service calls as edges, with error rates and average durations per edge.

Available at Performance > Service Map.

Data retention

Stored APM traces and trace resource stats use the APM trace retention window configured for your plan. See Billing & Plans for current limits.