How to double write DBM metrics to another endpoint?

[paymog]

I have DBM enabled for my datadog agent. I'm building another service to ingest metrics from the datadog agent and have found

    - name: DD_ADDITIONAL_ENDPOINTS
      value: '{"http://my-other-service/ingest": ["placeholder"]}'

which gets the agent and clusterchecks to double write metrics to the datadog platform AND this other endpoint. I can confirm that I see metrics like postgresql.transactions.open being ingested by my-other-service. However, I can't seem to figure out how to double write DBM specific metrics like postgresql.transactions.duration.max or postgresql.queries.count.

I have dbm enabled with cluster checks and I have the above environment configured for my cluster checks runner. I can see other DMB related metrics flowing but any metric that I see in Datadog with the following info doesn't seem to get double written

Do I need other config for the metrics from this subproduct to double write to my other service?

[EbrahimSolomon]

You can’t double-write DBM “Database Query Metrics” (e.g. postgresql.queries.count) with DD_ADDITIONAL_ENDPOINTS. That knob mirrors only the core metrics/events/service-checks pipeline. DBM data is sent by the DBM agent to a separate intake, so it bypasses additional endpoints.

Why you see some metrics mirrored: Things like postgresql.transactions.open are core integration/dogstatsd metrics → they follow the standard series intake and get mirrored. DBM query metrics don’t.

What to do instead (options):

1. Export from Datadog → use Metrics API (pull) or Metric Streams (push) to your system; confirm whether DBM query metrics are included for your account/region.
2. Aggregate & forward → create lower-cardinality rollups (dash/query) and export those.
3. If you must mirror at source, emit your own custom statsd metrics from the DB/integration sidecar (supported by additional endpoints), but that won’t be the DBM product metrics.

Note: DBM query metrics are intentionally high-cardinality; duplicating them 1:1 can be heavy. There’s no agent-side setting today that makes DBM query metrics double-write to arbitrary endpoints.