Skip to content

Go to the docs contents

OpenTelemetry

An OpenTelemetry endpoint for the metrics and traces of your app itself, which join what while already measures.

Updated November 21, 2026.

View as Markdown

OpenTelemetry OTLP endpoint: the app’s logs, metrics and traces poured into a single funnel

You, to your AI: Set up OpenTelemetry to track the time of database queries.

What your app receives

Your app receives these environment variables at every deployment:

VariableWhat it holds
OTEL_EXPORTER_OTLP_ENDPOINTThe OTLP/HTTP endpoint, reachable without opening outbound traffic.
OTEL_SERVICE_NAMEThe name the service appears under.

When to use it

For the app’s own metrics and traces, with an OpenTelemetry SDK.

How it works

An OTLP/HTTP endpoint (OTEL_EXPORTER_OTLP_ENDPOINT, reachable without opening egress) receives the app’s logs and metrics, which join while’s in the organization’s space (get_logs and observe_app tools). Its traces are kept 30 days and are read with observe_app { view: "traces" }.

What to know

Traces are read by service (OTEL_SERVICE_NAME, the project’s name by default) or by id. Of a trace that crosses several projects, only the environment’s part is returned.

Only OTLP/HTTP is accepted, not gRPC, with 4 MiB per send. Metrics arrive in protobuf (gzip, deflate or zstd). A metric with a name reserved for the platform (cnpg_, kube_, container_, while_, node_, envoy_, vm_…, and up), or a name attribute, is filed under appli_…, and the response says so (renommees).

Your agent’s MCP tools

Your agent handles it with the get_logs and observe_app tools.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh