Instrument your application

Maple ingests OpenTelemetry, so any OTLP exporter works unmodified. Each guide below walks through installing the SDK, pointing it at https://ingest.maple.dev with your ingest key, and verifying the first trace arrives. Prefer to skip the reading? Run maple-onboard in Claude Code and it instruments every service in the repo for you — see Getting started.

JavaScript & TypeScript

• Node.js Express, Fastify, Hono
• Next.js App Router, Pages Router, Edge
• Effect Official SDK · Node, Bun, Deno
• Cloudflare Workers Effect SDK · flush in waitUntil
• Browser Traces, web vitals, session replay

Python

• Python opentelemetry-sdk + auto-instrumentation
• FastAPI ASGI middleware, auto-instrumented routes
• Django Request, ORM and template spans

Java & Kotlin

• Java Java agent (zero-code) or manual SDK
• Spring Boot Auto-instrumented with the Java agent
• Kotlin Java agent, manual SDK, or the Ktor plugin
• Ktor Ktor OpenTelemetry plugin

Go, Rust, .NET & PHP

• Go otelhttp, otelgrpc, otelsql
• Rust tracing bridge · Axum, reqwest
• C# / .NET ASP.NET Core, HttpClient, EF Core
• Laravel PHP · Eloquent, queues, HTTP client

Frontend & product analytics

• Browser SDK Session replay, sessions, web vitals
• React, Vite & Next.js Mount the browser SDK once at app boot
• Effect Effect SDK in the browser
• Product events API Server-side track() over NDJSON

Infrastructure & data sources

• Kubernetes Helm collector · host, kubelet, cluster metrics
• Docker Single-container agent · per-container stats and logs
• Prometheus Managed scraping of any /metrics endpoint
• OpenTelemetry Collector Point any OTLP exporter at the ingest endpoint
• PlanetScale One-click org connect · connections, WAL, CPU
• WarpStream Consumer lag, request latency, object-store health
• GitHub Commits alongside your traces

Anything that speaks OTLP

If your language or framework is not listed, point its OpenTelemetry SDK (or an OpenTelemetry Collector) at the ingest endpoint with the standard environment variables. Ingest keys are project-scoped and write-only, so inlining them in your bootstrap source is fine too.

export OTEL_EXPORTER_OTLP_ENDPOINT="https://ingest.maple.dev"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer YOUR_INGEST_KEY"
export OTEL_SERVICE_NAME="my-service"

Maple reads the standard semantic conventions; the attributes it relies on for the service map, error grouping and sampling-aware throughput are listed in OpenTelemetry conventions. To develop against a local sink instead of the cloud, run Maple Local and point the endpoint at http://localhost:4318.

Missing a guide for your stack? Open an issue and tell us what you run.