Connect Datadog so Foggy can pull the full observability picture — metrics, logs, traces, monitors, and incidents — during investigations.Documentation Index
Fetch the complete documentation index at: https://docs.foggyhq.com/llms.txt
Use this file to discover all available pages before exploring further.
What Foggy can do
| Tool | Description |
|---|---|
| Metrics | Query time-series metrics |
| Logs | Search and read log streams |
| Traces | Read APM traces |
| Monitors | Read monitor definitions and state |
| Incidents | Read incident timelines and metadata |
Setup
Go to Connectors → Add Connector → Datadog and fill in the form.| Field | Required | Description |
|---|---|---|
| Name | Yes | Label for this connector (e.g. “Datadog-Production”) |
| API Key | Yes | Datadog → Organization Settings → API Keys → New Key |
| Application Key | Yes | Datadog → Personal Settings → Application Keys → New Key. Scopes (read): mcp_read + Monitors / Logs / APM / Metrics / Incidents read. |
| Site | Yes | One of: datadoghq.com (US1), us3.datadoghq.com, us5.datadoghq.com, datadoghq.eu, ap1.datadoghq.com, ap2.datadoghq.com. GovCloud is not supported. |
| Environments | No | Comma-separated env tags (e.g. prod,staging). Blank = all envs. |
Read-only. All required scopes are read-only — Foggy cannot modify monitors, acknowledge alerts, or create incidents.
Troubleshooting
- 403 on a subset of tools — the Application Key is missing one of the read scopes. Re-issue with all of
mcp_read, Monitors Read, Logs Read, APM Read, Metrics Read, Incidents Read. - Wrong data returned — check the Site field. Datadog partitions data per region; a wrong site returns data from a different organization.
- GovCloud — not supported. Contact support if GovCloud is a hard requirement.
Next steps
GitHub
Correlate Datadog incidents with recent commits and PRs.
Slack
Deliver investigation results to the right channel.