Datadog integration. Triage Datadog monitors as they fire and query metrics, logs and traces.
Praxen Inc. triages every Datadog monitor as it fires, queries your metrics, logs and APM traces to find the cause, and turns saved queries into checks.
Get started for freeWhat Praxen Inc. does with Datadog.
Alerts triaged on arrival
Every monitor that fires lands in Praxen Inc. as an issue, and an agent triages it the moment it does: real signal or noise, what it touches, and what changed right before.
Your dashboards become checks
Every query and chart your team saved in Datadog becomes a check: agents run it on a cadence and flag what doesn't look like normal. The curation you already did becomes detection.
Queried mid-investigation
Agents run Datadog metric, log, and trace queries while they work an issue, and every number is cited back to the query behind it.
First-class in the graph
Datadog joins the context graph as a source, so a spike lands next to the deploy, the config change, and the resources behind it.
How to set up Datadog
- Choose the Datadog site matching your account, such as US1, US3, US5, EU1 or AP1.
- Create an API key and an application key in Datadog Organization Settings and enter both into Praxen Inc.
- Validate and connect. Praxen Inc. creates a webhook named praxen and subscribes monitors to it.
Permissions and access
An unscoped application key inherits the user’s access. For a scoped key, the guide requires user_app_keys, logs_read_data, timeseries_query, metrics_read, monitors_read, monitors_write, monitors_downtime, dashboards_read, slos_read, hosts_read, events_read, incident_read, apm_read, aws_configuration_read and create_webhooks. Alert setup is not strictly read-only: monitor messages and tags are updated.
Discovery, refresh and the connected view
Agents query logs with Datadog syntax, metric time series, monitors, dashboards and incident context. Recurring reconciliation adds @webhook-praxen to monitor messages and praxen:managed to their tags. Include both in Terraform-managed monitors to avoid drift, while leaving the webhook itself managed by Praxen Inc. or importing it if your Terraform owns it.
Disconnect and revoke access
Disconnect Datadog in Praxen Inc., then revoke the application key and API key in Datadog. Review Terraform monitor configuration when removing the connection’s webhook references.
Datadog tools.
The calls Praxen Inc. can make to Datadog when it looks into an issue.
Datadog -
datadogApiCall any Datadog REST endpoint that lacks a dedicated tool -
datadogQueryMetricsQuery time-series metrics from Datadog -
datadogSearchLogsSearch and filter log entries in Datadog -
datadogDashboardsRead or create Datadog dashboards -
datadogMonitorsRead, create, or mute Datadog monitors -
datadogIncidentsRead Datadog incidents -
datadogSLOsRead or create Datadog Service Level Objectives (SLOs) -
datadogSpansQuery and aggregate Datadog APM spans and traces -
datadogListHostsList hosts reporting to Datadog -
datadogListEventsList events from Datadog -
datadogGetServiceDependenciesGet service dependency map from Datadog APM -
datadogCreateDowntimeSchedule a maintenance downtime in Datadog
Datadog setup and troubleshooting
Common questions.
How do I connect Datadog to Praxen Inc.?
Choose the Datadog site matching your account, such as US1, US3, US5, EU1 or AP1. Create an API key and an application key in Datadog Organization Settings and enter both into Praxen Inc. Validate and connect. Praxen Inc. creates a webhook named praxen and subscribes monitors to it.
What can Praxen Inc. read from Datadog?
Agents query logs with Datadog syntax, metric time series, monitors, dashboards and incident context. Recurring reconciliation adds @webhook-praxen to monitor messages and praxen:managed to their tags. Include both in Terraform-managed monitors to avoid drift, while leaving the webhook itself managed by Praxen Inc. or importing it if your Terraform owns it.