Skip to main content
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.

​
Exported telemetry

Exported telemetry mirrors the metrics and logs available in the E2B dashboard.

​
Metrics

E2B sends the following metrics to your endpoint. Each metric retains its name.
  • e2b.sandbox.cpu.used (Gauge) — CPU usage as a percentage.
  • e2b.sandbox.cpu.total (Gauge) — vCPUs allocated to the sandbox.
  • e2b.sandbox.ram.used (Gauge) — memory used, in bytes.
  • e2b.sandbox.ram.total (Gauge) — memory available, in bytes.
  • e2b.sandbox.ram.cache (Gauge) — memory used by the page cache, in bytes.
  • e2b.sandbox.disk.used (Gauge) — disk space used, in bytes.
  • e2b.sandbox.disk.total (Gauge) — disk space available, in bytes.
  • e2b.team.sandbox.created (Counter) — sandboxes started for the team.
  • e2b.team.sandbox.running (Gauge) — number of sandboxes currently running for the team.
Each sandbox metric includes the sandbox_id, team_id, build_id, and sandbox_type attributes. Each team metric includes team_id.

​
Logs

Logs include service_name: e2b. They include sandbox lifecycle events, such as sandbox start and stop events, along with other sandbox actions. These logs help you correlate sandbox activity with application behavior and infrastructure events. E2B sends telemetry using OTLP over HTTP/protobuf. Your endpoint should accept OTLP HTTP metrics and logs traffic, such as /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
For BYOC deployments, E2B can configure telemetry export from your BYOC environment to your own collector or backend.

​
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.
You can compare the received telemetry with the metrics and logs shown in the E2B dashboard. If telemetry does not appear, verify the OTLP endpoint URL, authentication headers, and any networking requirements such as allowlists or private connectivity.