Connect

Send telemetry

Point any OpenTelemetry exporter at the server and send the ingest key as a Bearer token:

export OTEL_EXPORTER_OTLP_ENDPOINT=https://maple.example.com
export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer%20<ingest key>"

The server takes OTLP over HTTP, as protobuf or JSON. It does not take gRPC, which some SDKs (Java, .NET) use by default, so set the protocol explicitly.

Maple’s own SDKs send their ingest key the same way, so an app already set up for Maple Cloud only needs two changes: the endpoint, and the ingest key, which becomes the server’s MAPLE_LOCAL_INGEST_KEY. The x-maple-ingest-key header works too.

Sign in

Open the server in a browser and sign in with the access token. Everyone uses the same token, and a sign-in lasts 30 days in that browser. There are no separate user accounts: to remove someone’s access, rotate the token.

Ten failed sign-ins within a minute pause the sign-in form for everyone for the rest of that minute. Browsers already signed in, and scripts sending the token as a Bearer header, keep working.

Query from the CLI

Inside the container, the CLI already has the access token and finds the server:

docker exec maple maple services
docker exec maple maple traces -s checkout --errors

With Docker Compose, use docker compose exec maple maple services.

From your own machine, point the CLI at the server:

export MAPLE_LOCAL_URL=https://maple.example.com
export MAPLE_LOCAL_ACCESS_TOKEN=<access token>
maple services

The CLI sends the token only to the host in MAPLE_LOCAL_URL (over the same scheme, so an https URL never gets it over plain http) and to this machine’s own addresses.

Scripts can call the query API directly with the same token:

curl https://maple.example.com/local/status \
  -H "Authorization: Bearer <access token>"