> ## 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. # Pingdom on Vortex IQ > Monitor Pingdom health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Pingdom 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) | **18** | **4** | **Build your own** | **Ready to build yours** | **10** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 18 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 | | ---------------------------- | ----------------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------- | | **Services Down** | Run operations | Alert band 0 / 1 | Checks fully unreachable. When the storefront URL is down, join to a commerce sibling to price the outage in \$/min. | | **Alerts Acknowledged** | Run operations | Merchant rule | Alerts a responder has acknowledged in the window - the leading edge of MTTA. | | **Alerts Firing** | Run operations | Merchant rule | Alert events raised by Pingdom checks in the window. | | **Apdex Score** | Customer experience | Alert band 0.94 / 0.85 | Satisfied vs tolerating vs frustrated response-time buckets rolled into one 0-1 score. | | **Avg Response Time** | Customer experience | Alert band 200 / 1500 | Average probe response time across all locations. | | **Error Rate** | Customer experience | Alert band 0.5 / 2 | Share of probe checks returning an error / down state. | | **Incidents Open** | Run operations | Alert band 0 / 3 | Outage windows currently open (down or degraded) across all checks. | | **Incidents Resolved (24h)** | Run operations | Merchant rule | Outage windows closed in the last 24 hours - recovery throughput. | | **Mean Time To Acknowledge** | Run operations | Alert band 300000 / 900000 | Median gap between an incident opening and a responder acknowledging it. | | **Mean Time To Resolve** | Run operations | Alert band 1800000 / 3600000 | Median gap between an incident opening and being resolved. | | **SLA Compliance** | Run operations | Alert band 99.9 / 99.5 | Uptime measured against the SLA target across the window. | | **Services Degraded** | Run operations | Alert band 0 / 2 | Checks responding slowly or intermittently but not fully down. | | **Services Healthy** | Run operations | Alert band 1 / 0 | Checks currently reporting an up / healthy state. | | **Throughput (req/min)** | Customer experience | Alert band 0 / -10 | Probe checks executed per minute across all locations. | | **Top Alerting Services** | Run operations | Merchant rule | Checks that raised the most alerts in the window - the noisiest / least-stable services. | | **Top Error Types** | Control risk and change | Merchant rule | Most common probe error reasons (timeout, connection refused, status code, DNS) across failing checks. | | **p95 Latency** | Customer experience | Alert band 800 / 1500 | 95th-percentile probe response time - the slow-tail experience. | | **p99 Latency** | Customer experience | Alert band 1500 / 3000 | 99th-percentile probe response time - worst-case slow checks. | ## 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 Pingdom 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 **9 read** and **1 write** operations across checks, actions, credits, results, summaryaverages, summaryoutages on Pingdom. 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=pingdom) | Resource | Read operations | Write operations | | ------------------- | --------------- | ---------------- | | checks | 2 | 1 | | actions | 1 | 0 | | credits | 1 | 0 | | results | 1 | 0 | | summaryaverages | 1 | 0 | | summaryoutages | 1 | 0 | | summaryperformances | 1 | 0 | | tmchecks | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected. ### Ready to build your first Pingdom 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.*