> ## 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.
[Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=datadog)
performance signals
automated checks
prepared fixes
proven workflows
API operations
### What you can achieve
Capabilities are grouped around merchant outcomes, not API terminology.
Monitor orders, fulfilment, delivery and settlement.
Find failures, leaks and risks before they cost sales.
Improve discovery, conversion, campaigns and repeat purchase.
Keep tracking, access and change under governed control.
Find storefront, speed, accessibility and journey problems.
### From connection to verified outcome
The controlled sequence every capability follows. Nothing changes a connected system without the approval step.
Authorise the source. Scopes are shown before access is granted.
Watch the signals against your own baselines, not universal defaults.
Run checks and gather evidence specific to your store.
Explain what happened, why it matters and the proposed action.
You review scope, risk and reversibility before anything changes.
Apply through governed connector operations.
Confirm the intended result and keep the receipt.
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.
### Monitor performance
62 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.
| Signal | Alert behaviour | What it tracks |
| ------------------------------------- | -------------------- | --------------------------------------------------------------------------------------------------- |
| **5xx Response Rate** | Alert band 0.5 / 2 | Description pending editorial review; the signal is live. |
| **API Monitor Failures (24h)** | Merchant rule | Description pending editorial review; the signal is live. |
| **Apdex / Error-Rate Anomaly** | Alert band 0 / 1 | Description pending editorial review; the signal is live. |
| **Container Restart Storm** | Merchant rule | Container Restart Storm over time. |
| **Error Budget Remaining** | Alert band 50 / 20 | Description pending editorial review; the signal is live. |
| **Error Rate** | Alert band 0.5 / 2 | Description pending editorial review; the signal is live. |
| **Error Spike Detection** | Merchant rule | Error Spike Detection over time. |
| **Error-level Log Rate** | Alert band 2 / 10 | Error-level Log Rate over time. |
| **Errors by Endpoint** | Merchant rule | Errors by Endpoint. |
| **Fatal-level Log Volume** | Alert band 0 / 100 | Fatal-level Log Volume over time. |
| **High-Cardinality Tag Warnings** | Merchant rule | High-cardinality tags blow up custom-metric counts and cost - warning surface from /api/v1/metrics. |
| **Host Uptime Distribution** | Watch only | Description pending editorial review; the signal is live. |
| **Hosts with CPU Saturation >85%** | Alert band 0 / 4 | Description pending editorial review; the signal is live. |
| **Hosts with Disk >90% Full** | Alert band 0 / 1 | Description pending editorial review; the signal is live. |
| **Hosts with Memory Saturation >85%** | Alert band 0 / 4 | Description pending editorial review; the signal is live. |
| **Hosts with Stale Agent (>24h)** | Alert band 0 / 1 | Description pending editorial review; the signal is live. |
| **Infrastructure Spend Trend** | Merchant rule | Description pending editorial review; the signal is live. |
| **JS Errors / Session** | Alert band 0.1 / 0.5 | Description pending editorial review; the signal is live. |
| **Monitor Coverage by Service** | Merchant rule | % of services with at least one error-rate + latency monitor wired up. Coverage gaps = blind spots. |
| **New Error Types (last 24h)** | Alert band 0 / 1 | Errors that didn't appear in the prior 7 days - highest-signal regression. |
| **Reporting Hosts** | Merchant rule | Description pending editorial review; the signal is live. |
| **SLO Compliance (current period)** | Merchant rule | SLO Compliance (current period), compared across items. |
| **Top Error Log Patterns** | Watch only | Top Error Log Patterns, broken down by row. |
| **Top Error Messages** | Merchant rule | Top Error Messages, broken down by row. |
| Signal | Alert behaviour | What it tracks |
| ----------------------------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------- |
| **Active Incidents** | Alert band 0 / 1 | Description pending editorial review; the signal is live. |
| **Alerts Summary** | Alert band 0 / 6 | Alerts for Alerts Summary. |
| **Browser Test Latency p95** | Alert band 2000 / 5000 | Browser Test Latency p95 over time. |
| **Currently Triggered Monitors** | Alert band 0 / 1 | Alerts for Currently Triggered Monitors. |
| **Custom Metric Quota Used** | Alert band 50 / 85 | Description pending editorial review; the signal is live. |
| **Days Until SLO Breach (forecast)** | Alert band 14 / 6 | Description pending editorial review; the signal is live. |
| **Ingestion Freshness (sec)** | Alert band 60 / 300 | Description pending editorial review; the signal is live. |
| **Log Indexing Cost Trend** | Merchant rule | Description pending editorial review; the signal is live. |
| **Log Indexing Volume Trend** | Merchant rule | Description pending editorial review; the signal is live. |
| **Log Volume (events/sec)** | Merchant rule | Volume spikes mean either real activity or runaway logging - both deserve attention. |
| **Mobile vs Desktop p95** | Watch only | Mobile vs Desktop p95, compared across items. |
| **Monitors Without Notification Channel** | Alert band 0 / 1 | Monitors that fire silently - when they trigger, nobody knows. Highest-leverage fix in this section. |
| **Monitors in 'No Data' State** | Alert band 0 / 1 | Lost telemetry - agent down, metric renamed, integration broken. Looks healthy but isn't. |
| **Operational Health Score** | Alert band 90 / 70 | Composite - apdex × inverse error-rate × inverse incident-count × SLO compliance. The CXO single-number. |
| **Page Load p95** | Alert band 2500 / 4000 | Description pending editorial review; the signal is live. |
| **SLO Burn Rate (1h)** | Alert band 1 / 14.4 | Multi-window burn-rate alerting - anything above 14.4× will eat the monthly budget in a day. |
| **Slowest Pages by Visits** | Alert band 2500 / 5000 | Slowest Pages by Visits. |
| **Sustained Threshold Breaches** | Alert band 0 / 1 | Alerts for Sustained Threshold Breaches. |
| **Synthetic Uptime** | Alert band 99.9 / 99.5 | Description pending editorial review; the signal is live. |
| **Throughput (req/s)** | Alert band 0 / -10 | Description pending editorial review; the signal is live. |
| **Uptime by Region** | Merchant rule | Uptime by Region. |
| **p95 Response Time** | Alert band 200 / 1000 | Description pending editorial review; the signal is live. |
| Signal | Alert behaviour | What it tracks |
| ------------------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Apdex Score** | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live. |
| **Apdex Trend** | Alert band 0.95 / 0.7 | Description pending editorial review; the signal is live. |
| **Database Query Latency p95** | Alert band 50 / 200 | Database Query Latency p95 over time. |
| **Deploy Markers vs Latency** | Watch only | Latency line with deploy events overlaid - turns 'why is it slow?' into 'which deploy did it'. |
| **Error Rate by Service** | Alert band 0.5 / 2 | Error Rate by Service. |
| **Latency & APM Monitors** | 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 surfac |
| **Throughput by Service** | Watch only | Throughput by Service. |
| **p99 Response Time** | Alert band 200 / 1000 | Description pending editorial review; the signal is live. |
| Signal | Alert behaviour | What it tracks |
| ----------------------------------------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Cart Abandonment During 5xx Spikes** | Merchant rule | Cart Abandonment During 5xx Spikes over time. |
| **Checkout Service Health × Sales** | Merchant rule | Latency on the checkout service overlaid with order volume - when checkout slows, sales follow. |
| **Conversion Drop During Incidents** | Merchant rule | Conversion Drop During Incidents, compared across items. |
| **Critical-Path Tests Status** | Merchant rule | Login, browse, add-to-cart, checkout - the customer journey synthetics. Any failure = revenue at risk. |
| **Revenue Lost / Min (active incidents)** | Merchant rule | Live \$/min loss while incidents are open. Stops being academic and starts being the COO's number. |
| **Revenue at Risk (live)** | Merchant rule | Datadog state × commerce-sibling baseline = \$/hour at risk while the incident is open. The single most-valuable card in this manifest. |
| Signal | Alert behaviour | What it tracks |
| ----------------------------------- | ---------------- | -------------------------------------------------------------------------------------------- |
| **Frustrated User Sessions** | Alert band 1 / 5 | Sessions where load >4s or rage-click detected - proxy for conversion drop. |
| **Recently Flapped Monitors (24h)** | Alert band 0 / 4 | Monitors flipping repeatedly = noisy / threshold wrong / real instability - all need triage. |
### 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. Open a check for the detail.
**Severity** critical · **Outcome** Customer experience · **Fix status** Report only
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 work, and a rate this high is an active problem, not background noise.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `MONITORING-ERROR-001`
**Severity** high · **Outcome** Customer experience · **Fix status** Report only
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 performance complaints are about to start, even before anyone files one.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `MONITORING-APDEX-001`
**Severity** medium · **Outcome** Protect revenue · **Fix status** Report only
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 a revenue issue wearing a performance-metric label.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `MONITORING-PERF-001`
**Severity** medium · **Outcome** Run operations · **Fix status** Report only
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 requests it would otherwise handle, two very different problems that look identical in this one number.
Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps.
Reference: `MONITORING-THROUGHPUT-001`
#### Build your own automated fixes
Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 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 **over 13,000 operations across more than 200 connectors** to automate the work in your own words.
Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution.
[Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=datadog)
#### 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.
| 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.