Stack Monitors
Monitor Datadog Infrastructure with Crowswatch
Monitor infrastructure metrics, APM traces, and log analytics from your Datadog organisation directly from Crowswatch.
What This Integration Provides
- Infrastructure metrics: host and container CPU, memory, disk, and network
- APM: service latency, error rates, and throughput from distributed traces
- Monitors: current state of all Datadog monitors (OK / Alert / Warn / No Data)
- Log analytics: log volume, error count, and pattern trends
- Dashboards: visibility into your key Datadog dashboard metrics
- Service health: service-level indicators across your monitored stack
Requirements
| Requirement | Detail |
|---|---|
| Datadog account | Any plan |
| API key | Organisation-level key |
| Application key | User-scoped key with read permissions |
| Datadog site | Your organisation's Datadog URL (e.g. datadoghq.com or datadoghq.eu) |
| Estimated setup time | ~10 minutes |
Step 1: Generate Credentials
Reading data from Datadog requires both an API key and an Application key.
- The API key authenticates the source (your organisation)
- The Application key inherits the permissions of the user who created it and controls what data can be accessed
To create an API key:
- Log in to your Datadog organisation
- Go to Organization Settings → API Keys
- Click New Key
- Name it (e.g.
crowswatch-monitor) - Click Create Key and copy the value immediately
To create an Application key:
- Go to Organization Settings → Application Keys
- Click New Key
- Name it (e.g.
crowswatch-monitor) - Click Add Scopes and add the following read-only scopes:
Scope Purpose metrics_read Read metric data monitors_read Read monitor state and history logs_read_data Read log data apm_read Read APM traces and services dashboards_read Read dashboard definitions - Click Create Application Key and copy the value immediately
Step 2: Locate Required IDs
Datadog Site
Your Datadog site determines the API base URL. Check which URL you log in at:
| Login URL | Site |
|---|---|
| app.datadoghq.com | US1 (default) |
| us3.datadoghq.com | US3 |
| us5.datadoghq.com | US5 |
| app.datadoghq.eu | EU |
| ap1.datadoghq.com | AP1 |
You will select your site in the Crowswatch connection form.
Step 3: Add Credentials to Crowswatch
Navigate to: Crowswatch → Add Service → Datadog
| Field | Value |
|---|---|
| API Key | The API key from Step 1 |
| Application Key | The Application key from Step 1 |
| Site | Your Datadog site (e.g. datadoghq.com) |
Available Metrics
Infrastructure
- Host CPU utilisation (%)
- Memory used / available
- Disk read/write throughput
- Network in/out (bytes)
- Container count
APM
- Service request rate (requests/sec)
- Service error rate (%)
- Service latency (p50, p75, p95, p99)
- Trace volume by service
Monitors
- Monitor count by state (OK, Alert, Warn, No Data)
- Recently triggered monitors
- Monitor state history
Logs
- Log volume by service or environment
- Error log count
- Log ingestion rate
Connect
- Enter your API Key, Application Key, and Site in the Crowswatch form
- Click Verify to confirm the credentials are valid
- Select the metrics and services you want to track
- Click Connect
Security
- Application keys inherit the permissions of the creating user, so create the key under a user with only the permissions listed above
- Use scoped Application keys (with specific scopes selected) rather than unscoped keys
- Do not use Admin-level Application keys for monitoring
- Rotate both keys periodically and update them in Crowswatch when you do
Troubleshooting
Authentication error
Confirm both the API key and Application key are correct. Both are required, and neither alone is sufficient for reading data. Verify you are using the correct Datadog site.
Permission denied on specific metrics
Confirm the Application key has the required scope (e.g. logs_read_data for log metrics). Scopes can be checked and updated in Organization Settings → Application Keys.
No data appearing
Check that the API key is active and belongs to the correct organisation. Confirm that Datadog is actually receiving data from your infrastructure.
Wrong site selected
If you see authentication errors despite correct credentials, double-check your site selection. US1 and EU credentials cannot be swapped.