What you’ll get: ewake can query your Datadog metrics, logs, traces, APM data, and monitors in real time. This is the primary data source for alert investigation and root cause analysis.
Prerequisites
- A Datadog account with admin or org-level access to create API and Application keys
- Access to your ewake dashboard
Configuration
1
Log in to Datadog
Navigate to your Datadog instance:
- US: app.datadoghq.com
- EU: app.datadoghq.eu
Use the EU URL if your Datadog account is hosted in Europe. The two regions are separate accounts, using the wrong URL will cause authentication errors at the connection step.
2
Open Organization Settings
Hover over your name in the bottom left → click Organization Settings.
3
Create an API Key
Go to API Keys → click New Key. Name it
ewake and copy the key immediately.Copy the key now, you won’t be able to see it again after closing the modal.
4
Create an Application Key
Go to Application Keys → click New Key. Name it Copy the Application key.
ewake.Grant it the following read-only scopes:These six are everything ewake calls. Don’t add
debugger_read, llm_observability_read, error_tracking_read, events_read, logs_read_archives, logs_read_index_data, apm_api_catalog_read, apm_pipelines_read or apm_service_ingest_read, no ewake code path uses them, so they widen your exposure for nothing.5
Open the Datadog integration modal in ewake
In your ewake dashboard, go to Integrations → Datadog → click Connect with API key.
6
Paste your credentials
7
Test and save
Click Test connection. Ewake probes
monitors_read, logs_read_data, metrics_read, apm_read and dashboards_read and reports each as granted or missing, so you can fix the key before saving. Then click Save.Datadog is connected. Ewake can now access your observability data.