E2B can export OpenTelemetry (OTel) metrics and logs to any OpenTelemetry-compatible destination with an OTLP HTTP endpoint. This lets you integrate E2B telemetry with your existing monitoring and observability stack.Documentation Index
Fetch the complete documentation index at: https://e2b.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Exported telemetry
Exported telemetry mirrors the metrics and logs available in the E2B dashboard.- Metrics are emitted under the
e2b.*namespace. - Logs include
service_name: e2b.
/v1/metrics and /v1/logs paths on an OpenTelemetry Collector.
Refer to your provider’s documentation for specific OTLP endpoint details and authentication requirements.
Setup
During onboarding, provide E2B with the endpoint details for your OTel collector or observability backend:- OTLP HTTP endpoint URL
- Authentication requirements, such as static headers or bearer tokens
Delivery behavior
Telemetry export is best effort. E2B tries to send metrics and logs continuously and retries whenever possible. If your endpoint is unavailable, unreachable, or rejects telemetry, some metrics or logs may be delayed or dropped.Confirm telemetry delivery
After E2B enables the export, start one or more sandboxes and wait a few minutes for telemetry to reach your destination. In your collector or observability backend, confirm that:- Metrics are emitted under the
e2b.*namespace. - Logs include
service_name: e2b.