Platform
Send telemetry over OTLP/gRPC
The ingest endpoint now accepts OTLP over gRPC as well as HTTP, so exporters that default to gRPC work without a protocol change.
Maple’s ingest endpoint now accepts OTLP over gRPC, on the same host and port as OTLP over HTTP. Java, .NET, Python and the OpenTelemetry Collector often default to gRPC, and they can now send traces, logs and metrics to Maple as they are configured:
export OTEL_EXPORTER_OTLP_ENDPOINT="https://ingest.maple.dev" # https://ingest.eu.maple.dev for EU organizations
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer YOUR_INGEST_KEY"
export OTEL_EXPORTER_OTLP_PROTOCOL="grpc"gzip compression, request limits and ingest keys work the same as over HTTP. Errors come back as
gRPC status codes, and the ones worth retrying are UNAVAILABLE, which exporters already retry.
See the Ingest API reference.