Open Source Dash0 Alternatives

Most teams end up with a metrics system, a log store and a tracing tool that know nothing about each other, so debugging means carrying a timestamp between three browser tabs. SigNoz puts logs, metrics, traces, alerts, dashboards and exceptions in one product, so context travels with you instead of being reconstructed by hand.

It is built on OpenTelemetry, which means you instrument once with an open standard and keep ownership of the telemetry. Storage is a single columnar database chosen for high-cardinality, high-volume workloads, and queries can be written through a visual builder, PromQL or ClickHouse SQL.

The monitoring surfaces it ships with cover most of what a production team watches.

• APM: service latency, error rate, throughput, Apdex, top endpoints, database calls and external calls.
• Log management: ingest, search, aggregate and correlate logs against traces and metrics.
• Infrastructure monitoring: Kubernetes clusters, pods, nodes and workloads alongside host CPU, memory, disk and network.
• Distributed tracing: flamegraphs, waterfalls, span events and trace analytics, plus funnels that expose drop-offs in a request flow.
• LLM observability: traces for LLM apps and RAG pipelines covering prompts, tool calls, tokens, latency and cost.

The community edition is free and runs on your own infrastructure through Docker, Kubernetes or Linux, with managed cloud and enterprise tiers for teams that need compliance, RBAC, custom retention and support. An MCP server carries telemetry into coding agents for teams working that way.

Uptrace is an open source APM covering distributed tracing, metrics and logs behind a single interface. Instead of running a separate system for each signal, you send everything through OpenTelemetry and query it from one place, with a query builder, dashboards and alerting on top.

Storage is ClickHouse, with PostgreSQL holding metadata such as metric names and alert definitions. That pairing is where the cost argument comes from: a one kilobyte span compresses to roughly forty bytes on disk, a single core processes more than ten thousand spans per second, and one server can carry billions of spans and metrics.

Querying and alerting are built around shapes engineers already know.

• SQL-like span queries: spans and logs are aggregated with a language close to SQL.
• PromQL-like metric queries: metrics use a syntax Prometheus users will recognize.
• Prebuilt dashboards: more than fifty dashboards appear automatically once matching metrics start arriving.
• Alerting: rules over spans, logs and metrics notify by email, Slack, webhook or AlertManager.
• Grafana compatibility: Uptrace can be configured as a Tempo or Prometheus data source.

Ingestion accepts OpenTelemetry, Prometheus, Vector, FluentBit and CloudWatch among others, and a service graph plus chart annotations tie deploys to what the charts show. Users and projects are managed from a YAML config, and single sign-on works over OpenID Connect with Keycloak, Google Cloud and Cloudflare. A cloud demo needs no login, and a Docker example gets a local instance running quickly.

Maple collects traces, logs, and metrics through OpenTelemetry and stores them in ClickHouse. The point is a single place to look when a request goes wrong, without the instrumentation being tied to a vendor that owns the query language it is read with.

The repository is a Bun monorepo. A TanStack Router single-page application serves the dashboard, an Effect-based HTTP API sits behind it carrying an MCP server and AI triage, a separate OTLP ingest gateway handles key authentication and organization enrichment before forwarding to a collector, and an alerting worker evaluates rules on a cron schedule. Shared packages hold the HTTP contracts, the query engine, and UI primitives, while application state lives in PostgreSQL.

The choices to make up front are how it runs and how people sign in.

• Local binary: a Homebrew install and one start command bring up OTLP ingest, embedded ClickHouse, and the dashboard together.
• Docker Compose: the multi-service stack of API, web, ingest, and OTEL collector on local ports.
• Cloudflare Workers: deployment through Alchemy, with PlanetScale Postgres reached over Hyperdrive.
• Clerk auth: organizations come from a Clerk application, with optional networkless token verification.
• Self-hosted auth: a single root password issues bearer sessions valid for twelve hours, capped at seven days from sign-in.

Ingest keys are managed per organization and can be rerolled independently, with private keys encrypted at rest and looked up through non-reversible HMAC hashes. Bun 1.3 or later is the only prerequisite for the code, and a native SwiftUI iOS client lives in the same repository.