OpenTelemetry

Maple runs on OpenTelemetry

Traces, logs and metrics all arrive over OTLP. There is no Maple agent to install and no Maple SDK to depend on.

The standard

What is OpenTelemetry?

OpenTelemetry is the CNCF's open standard for collecting telemetry. It defines the APIs, SDKs and wire protocol (OTLP) that applications use to produce traces, logs and metrics, independent of any vendor.

It has SDKs for every major language and contributions from hundreds of companies. Most new instrumentation is written against it.

Our approach

Why we build on OpenTelemetry

Switch backends without code changes

Your instrumentation doesn't depend on Maple. Sending it somewhere else is a config change.

One standard, all signals

Traces, logs and metrics share one data model and carry the same trace context, so they link up without glue code.

Run by the community

Backed by the CNCF and hundreds of contributors. The spec is governed by the community, and no single vendor sets its roadmap.

Broad language support

Official SDKs for Go, Java, Python, JavaScript, .NET, Rust, and more. Auto-instrumentation is available for most frameworks.

Instrument once

Instrumentation you write today keeps working with whatever backend you use next.

Collector pipelines

Receivers, processors and exporters let you filter, sample and route telemetry before it reaches any backend.

Spec compliance

How Maple follows the spec

Native OTLP ingest

Send telemetry over OTLP/HTTP as protobuf or JSON. There is no Maple-specific format.

Semantic conventions

Maple reads the OTel semantic conventions for HTTP, database, RPC, and messaging spans and builds its views from them.

All three signals

Traces, logs, and metrics are each stored, queried, and correlated with the others.

Collector compatible

Use the OpenTelemetry Collector to route, filter, and batch telemetry before sending it to Maple.

Any OTel SDK

Works with every official OTel SDK. If it sends OTLP, Maple accepts it.

Context propagation

W3C Trace Context is supported. Spans and logs from different services correlate by trace ID.

Ecosystem

Works with your existing OTel setup

Already using the OpenTelemetry Collector, auto-instrumentation agents, or OTel SDKs? Point your OTLP exporter at Maple with an ingest key. Nothing else in your pipeline changes.

Maple is the backend at the end of that pipeline. It stores and queries what your pipeline already produces.

Explore more

Related features

See your first trace today.

Add the SDK, point your OTLP exporter at Maple, and traces arrive.

maple.dev: observability on OpenTelemetry