moneat.io

Getting Started

Create your account, create a service, and connect your first telemetry source.

Create your account

  1. 1
    Sign up
    Visit moneat.io/signup to create your account. You can sign up with email/password, GitHub, or Apple.
  2. 2
    Complete onboarding
    Create your organization and first service. A service is the application, worker, job, or system that will send telemetry to Moneat.
  3. 3
    Choose a telemetry source
    For new services, start with OpenTelemetry. If you already have Sentry-compatible SDKs or a Datadog Agent fleet, connect those sources without changing your application model.

Choose a source

Moneat stores errors, traces, metrics, logs, replays, releases, and feedback in one telemetry model. The source you connect only decides how data gets into Moneat.

SourceBest forSetup
OpenTelemetryNew services, vendor-neutral logs/traces/metrics, Collector pipelinesOpenTelemetry setup
Sentry-compatible SDKsExisting Sentry SDK instrumentation, errors, replays, release/source-map workflowsSentry-compatible SDKs
Datadog AgentExisting Datadog Agent fleets, host/container telemetry, APM/log/profile intakeDatadog Agent setup

Start with OpenTelemetry

Create an OTLP API key from Settings -> API Keys -> OpenTelemetry, then configure your SDK or Collector to send data to Moneat. Use https://api.moneat.io for Moneat Cloud, or your self-hosted backend URL.

Shell
export OTEL_SERVICE_NAME=checkout-api
export OTEL_RESOURCE_ATTRIBUTES="deployment.environment.name=production,service.version=1.2.3"
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=https://api.moneat.io/v1/traces
export OTEL_EXPORTER_OTLP_METRICS_ENDPOINT=https://api.moneat.io/v1/metrics
export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT=https://api.moneat.io/v1/logs
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer <MONEAT_OTLP_API_KEY>"

After the service sends its first spans, metrics, or logs, check Performance, Logs, and Services in the dashboard. Moneat uses OpenTelemetry resource attributes such as service.name, service.version, and deployment.environment.name for service and release correlation.

Service mapping

If an observed service.name does not match an existing Moneat service, map it from Settings -> API Keys -> OpenTelemetry so dashboards and filters route telemetry correctly.

Keep existing Sentry-compatible SDKs

If your application already uses a Sentry SDK, keep it and replace the DSN with the Moneat service DSN from service settings:

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

This source is the richest path for exception events, breadcrumbs, session replay, and source-map upload workflows. See Sentry-compatible SDKs for platform-specific setup.

Connect a Datadog Agent

If you already run Datadog Agents, create an agent key from Settings -> API Keys -> Datadog and point the agent intake URLs at Moneat. This keeps host, container, log, APM, profile, and supported infrastructure telemetry flowing while Moneat normalizes it into the same service views.

See Datadog Agent setup for the full agent configuration.

Verify ingestion

Use the dashboard views that match the signal you sent:

  • Services - Confirm the service appears with the expected telemetry sources.
  • Performance - Confirm traces and spans appear for OTLP, Sentry-compatible, or Datadog APM traffic.
  • Logs - Search for structured logs by service, level, and attributes.
  • Issues - Trigger a test exception if you are using a Sentry-compatible SDK.
  • Monitoring - Confirm host, container, database, or network telemetry from compatible agents.

Next steps