Datadog

This recipe ships data emitted by msb-metrics. See the msb-metrics page for the flag reference, metric names, and deployment constraints.

The recommended path is to point msb-metrics at the Datadog Agent with OTLP ingestion enabled. The agent handles temporality conversion, metric translation, and shipping to Datadog’s backend.

Enable OTLP on the Datadog Agent

Edit datadog.yaml to enable the OTLP receiver on standard ports:

otlp_config:
  receiver:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318

Restart the agent.

Point msb-metrics at the agent

msb-metrics otel --endpoint=http://localhost:4317

Verify

Boot a sandbox and open Datadog → Metrics → Explorer. Query microsandbox.cpu.utilization. Sandbox identity (sandbox.name, sandbox.id) and any resource attributes (service.name, etc.) appear as tags.

Direct OTLP intake

Datadog also exposes a direct OTLP HTTP intake at https://otlp.datadoghq.com/v1/metrics (region-specific) that avoids the agent. It expects delta temporality for metrics, while msb-metrics emits cumulative values, so direct intake needs a temporality conversion step. If you need direct intake, put an otel-collector with the cumulativetodelta processor between msb-metrics and Datadog. Otherwise, stick with the agent path above, which converts temporality for you.

Reference

PrometheusShip msb-metrics output directly to Prometheus's OTLP ingestion endpoint

⌘I

Docker

Guest

Metrics backends

Direct OTLP intake

Reference

​Direct OTLP intake

​Reference

Direct OTLP intake

Reference