> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Datadog on Vortex IQ > Monitor Datadog health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Datadog health, cost and reliability signals, and catch incidents and runaway spend early. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) | **62** | **4** | **Build your own** | **Ready to build yours** | **1,757** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 62 performance signals. Signals with an alert band can raise Nerve Centre alerts; every signal supports a merchant-configured watcher. | Signal | Outcome | Alert behaviour | What it tracks | | ----------------------------------------- | ----------------------- | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Alerts Summary** | Run operations | Alert band 0 / 6 | Alerts for Alerts Summary. | | **Checkout Service Health × Sales** | Protect revenue | Merchant rule | Latency on the checkout service overlaid with order volume - when checkout slows, sales follow. | | **Critical-Path Tests Status** | Protect revenue | Merchant rule | Login, browse, add-to-cart, checkout - the customer journey synthetics. Any failure = revenue at risk. | | **Currently Triggered Monitors** | Run operations | Alert band 0 / 1 | Alerts for Currently Triggered Monitors. | | **Frustrated User Sessions** | Grow revenue | Alert band 1 / 5 | Sessions where load >4s or rage-click detected - proxy for conversion drop. | | **Operational Health Score** | Run operations | Alert band 90 / 70 | Composite - apdex × inverse error-rate × inverse incident-count × SLO compliance. The CXO single-number. | | **Revenue Lost / Min (active incidents)** | Protect revenue | Merchant rule | Live \$/min loss while incidents are open. Stops being academic and starts being the COO's number. | | **Revenue at Risk (live)** | Protect revenue | Merchant rule | Datadog state × commerce-sibling baseline = \$/hour at risk while the incident is open. The single most-valuable card in this manifest. | | **SLO Burn Rate (1h)** | Run operations | Alert band 1 / 14.4 | Multi-window burn-rate alerting - anything above 14.4× will eat the monthly budget in a day. | | **5xx Response Rate** | Control risk and change | Alert band 0.5 / 2 | Description pending editorial review; the signal is live. | | **Active Incidents** | Run operations | Alert band 0 / 1 | Description pending editorial review; the signal is live. | | **Error Rate** | Control risk and change | Alert band 0.5 / 2 | Description pending editorial review; the signal is live. | | **Synthetic Uptime** | Run operations | Alert band 99.9 / 99.5 | Description pending editorial review; the signal is live. | | **Throughput (req/s)** | Run operations | Alert band 0 / -10 | Description pending editorial review; the signal is live. | | **p95 Response Time** | Run operations | Alert band 200 / 1000 | Description pending editorial review; the signal is live. | | **Browser Test Latency p95** | Run operations | Alert band 2000 / 5000 | Browser Test Latency p95 over time. | | **Cart Abandonment During 5xx Spikes** | Protect revenue | Merchant rule | Cart Abandonment During 5xx Spikes over time. | | **Container Restart Storm** | Control risk and change | Merchant rule | Container Restart Storm over time. | | **Conversion Drop During Incidents** | Protect revenue | Merchant rule | Conversion Drop During Incidents, compared across items. | | **Database Query Latency p95** | Customer experience | Alert band 50 / 200 | Database Query Latency p95 over time. | | **Deploy Markers vs Latency** | Customer experience | Watch only | Latency line with deploy events overlaid - turns 'why is it slow?' into 'which deploy did it'. | | **Error Rate by Service** | Customer experience | Alert band 0.5 / 2 | Error Rate by Service. | | **Error Spike Detection** | Control risk and change | Merchant rule | Error Spike Detection over time. | | **Error-level Log Rate** | Control risk and change | Alert band 2 / 10 | Error-level Log Rate over time. | | **Errors by Endpoint** | Control risk and change | Merchant rule | Errors by Endpoint. | | **Fatal-level Log Volume** | Control risk and change | Alert band 0 / 100 | Fatal-level Log Volume over time. | | **High-Cardinality Tag Warnings** | Control risk and change | Merchant rule | High-cardinality tags blow up custom-metric counts and cost - warning surface from /api/v1/metrics. | | **Latency & APM Monitors** | Customer experience | Merchant rule | Monitors tagged latency / apm and how many are firing. Per-endpoint p95 slicing needs a by-resource\_name query the engine does not run, so this surfaces the monitors watc | | **Log Volume (events/sec)** | Run operations | Merchant rule | Volume spikes mean either real activity or runaway logging - both deserve attention. | | **Mobile vs Desktop p95** | Run operations | Watch only | Mobile vs Desktop p95, compared across items. | | **Monitor Coverage by Service** | Control risk and change | Merchant rule | % of services with at least one error-rate + latency monitor wired up. Coverage gaps = blind spots. | | **Monitors Without Notification Channel** | Run operations | Alert band 0 / 1 | Monitors that fire silently - when they trigger, nobody knows. Highest-leverage fix in this section. | | **Monitors in 'No Data' State** | Run operations | Alert band 0 / 1 | Lost telemetry - agent down, metric renamed, integration broken. Looks healthy but isn't. | | **New Error Types (last 24h)** | Control risk and change | Alert band 0 / 1 | Errors that didn't appear in the prior 7 days - highest-signal regression. | | **Recently Flapped Monitors (24h)** | Grow revenue | Alert band 0 / 4 | Monitors flipping repeatedly = noisy / threshold wrong / real instability - all need triage. | | **SLO Compliance (current period)** | Control risk and change | Merchant rule | SLO Compliance (current period), compared across items. | | **Slowest Pages by Visits** | Run operations | Alert band 2500 / 5000 | Slowest Pages by Visits. | | **Sustained Threshold Breaches** | Run operations | Alert band 0 / 1 | Alerts for Sustained Threshold Breaches. | | **Throughput by Service** | Customer experience | Watch only | Throughput by Service. | | **Top Error Log Patterns** | Control risk and change | Watch only | Top Error Log Patterns, broken down by row. | | **Top Error Messages** | Control risk and change | Merchant rule | Top Error Messages, broken down by row. | | **Uptime by Region** | Run operations | Merchant rule | Uptime by Region. | | **API Monitor Failures (24h)** | Control risk and change | Merchant rule | Description pending editorial review; the signal is live. | | **Apdex / Error-Rate Anomaly** | Control risk and change | Alert band 0 / 1 | Description pending editorial review; the signal is live. | | **Apdex Score** | Customer experience | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live. | | **Apdex Trend** | Customer experience | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live. | | **Custom Metric Quota Used** | Run operations | Alert band 50 / 85 | Description pending editorial review; the signal is live. | | **Days Until SLO Breach (forecast)** | Run operations | Alert band 14 / 6 | Description pending editorial review; the signal is live. | | **Error Budget Remaining** | Control risk and change | Alert band 50 / 20 | Description pending editorial review; the signal is live. | | **Host Uptime Distribution** | Control risk and change | Watch only | Description pending editorial review; the signal is live. | | **Hosts with CPU Saturation >85%** | Control risk and change | Alert band 0 / 4 | Description pending editorial review; the signal is live. | | **Hosts with Disk >90% Full** | Control risk and change | Alert band 0 / 1 | Description pending editorial review; the signal is live. | | **Hosts with Memory Saturation >85%** | Control risk and change | Alert band 0 / 4 | Description pending editorial review; the signal is live. | | **Hosts with Stale Agent (>24h)** | Control risk and change | Alert band 0 / 1 | Description pending editorial review; the signal is live. | | **Infrastructure Spend Trend** | Control risk and change | Merchant rule | Description pending editorial review; the signal is live. | | **Ingestion Freshness (sec)** | Run operations | Alert band 60 / 300 | Description pending editorial review; the signal is live. | | **JS Errors / Session** | Control risk and change | Alert band 0.1 / 0.5 | Description pending editorial review; the signal is live. | | **Log Indexing Cost Trend** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Log Indexing Volume Trend** | Run operations | Merchant rule | Description pending editorial review; the signal is live. | | **Page Load p95** | Run operations | Alert band 2500 / 4000 | Description pending editorial review; the signal is live. | | **Reporting Hosts** | Control risk and change | Merchant rule | Description pending editorial review; the signal is live. | | **p99 Response Time** | Customer experience | Alert band 200 / 1000 | Description pending editorial review; the signal is live. | ## Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. | Check | Severity | Outcome | Why it matters | Fix status | | ------------------------------------------- | -------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **Error rate above 2%** | critical | Customer experience | More than 1 in 50 requests is failing right now. Depending on which endpoints are affected, this can mean pages failing to load, checkout steps failing silently, or background jobs dropping | Report only | | **Apdex score below 0.85** | high | Customer experience | Apdex below 0.85 means a meaningful share of visits are experiencing the site as slow or frustrating rather than satisfying, using the same industry-standard scoring that tells you when perf | Report only | | **Avg response time above 1500ms** | medium | Protect revenue | Average response time over 1.5 seconds is well past the point where shoppers notice the delay, and slow response times are a documented driver of higher bounce and lower conversion; this is | Report only | | **Throughput dropped > 30% week-over-week** | medium | Run operations | Requests handled dropped more than 30% versus the prior week. This can mean genuinely lower traffic (worth knowing on its own) or it can mean the application is silently failing to serve req | Report only | ### Build your own automated fixes 4 checks report findings on Datadog today. Turn any finding into an automated fix with a Vortex IQ workflow: **13,885 read and write operations across 229 connectors** are available as building blocks, with approval, verification and rollback on every change. ## Automate approved work Vortex IQ is integrated with **752 read** and **1,005 write** operations across apikeys, downtimes, users, applicationkeys, dashboards, appbuilderapps on Datadog. Combine them with anything from the **13,885 operations across 229 connectors** to automate the work in your own words. Changes follow the merchant's configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. Read-only operations do not modify the connected system. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=datadog) | Resource | Read operations | Write operations | | ------------------------- | --------------- | ---------------- | | apikeys | 4 | 6 | | downtimes | 4 | 6 | | users | 4 | 6 | | applicationkeys | 4 | 5 | | dashboards | 2 | 5 | | appbuilderapps | 2 | 4 | | events | 4 | 2 | | integrationaweventbridges | 2 | 4 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first Datadog workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. *** *Generated from the connector capability graph. Counts reflect the servable registry after alias normalisation and de-duplication, and refresh automatically when the registry changes.*