What the Datadog integration enables
| Feature | Requires |
|---|---|
| OTel health reports | API key + App key |
| Reliability reports | API key + App key |
| Create dashboards | App key with dashboards_write |
| Create monitors | App key with monitors_write |
| Automatic webhook registration | App key with integrations_write |
Updating credentials
- Go to Integrations → Datadog card.
- Click Edit.
- Update the API key, application key, or site.
- Click Save.
Datadog sites
| Site | URL | site value |
|---|---|---|
| US1 (default) | datadoghq.com | datadoghq.com |
| EU | datadoghq.eu | datadoghq.eu |
| US3 | us3.datadoghq.com | us3.datadoghq.com |
| US5 | us5.datadoghq.com | us5.datadoghq.com |
| AP1 | ap1.datadoghq.com | ap1.datadoghq.com |
OTel metric naming in Datadog
The Datadog OTel exporter converts OTLP counter metrics by dropping the_total suffix:
otelcol_exporter_queue_size, otelcol_process_memory_rss) are unchanged.
Obsy’s queries already use the correct Datadog names. If you’re writing your own Datadog monitors for OTel collector health, use the names without _total.
Webhook auto-registration
When you click Create Monitors, Obsy automatically registers theobsy webhook in your Datadog organization using your application key. After registration, Obsy adds @webhook-obsy to all 11 generated monitors.
You can verify the webhook in Datadog: Integrations → Webhooks → obsy.