> ## 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.

[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=pingdom)

<CardGroup cols={5}>
  <Card title="18">
    performance signals
  </Card>

  <Card title="4">
    automated checks
  </Card>

  <Card title="Build your own">
    automated fixes
  </Card>

  <Card title="Ready to build yours">
    workflows
  </Card>

  <Card title="10">
    API operations
  </Card>
</CardGroup>

<Tabs>
  <Tab title="Overview">
    ### What you can achieve

    Capabilities are grouped around merchant outcomes, not API terminology.

    <CardGroup cols={2}>
      <Card title="Run operations">
        Monitor orders, fulfilment, delivery and settlement.
      </Card>

      <Card title="Customer experience">
        Find storefront, speed, accessibility and journey problems.
      </Card>

      <Card title="Control risk and change">
        Keep tracking, access and change under governed control.
      </Card>

      <Card title="Protect revenue">
        Find failures, leaks and risks before they cost sales.
      </Card>
    </CardGroup>

    ### From connection to verified outcome

    The controlled sequence every capability follows. Nothing changes a connected system without the approval step.

    <Steps>
      <Step title="Connect">
        Authorise the source. Scopes are shown before access is granted.
      </Step>

      <Step title="Monitor">
        Watch the signals against your own baselines, not universal defaults.
      </Step>

      <Step title="Detect">
        Run checks and gather evidence specific to your store.
      </Step>

      <Step title="Recommend">
        Explain what happened, why it matters and the proposed action.
      </Step>

      <Step title="Approve">
        You review scope, risk and reversibility before anything changes.
      </Step>

      <Step title="Execute">
        Apply through governed connector operations.
      </Step>

      <Step title="Verify">
        Confirm the intended result and keep the receipt.
      </Step>
    </Steps>

    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.
  </Tab>

  <Tab title="Monitor (18)">
    ### Monitor performance

    18 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system.

    <AccordionGroup>
      <Accordion title="Run operations (11 signals)">
        | Signal                       | Alert behaviour              | What it tracks                                                                                                       |
        | ---------------------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------- |
        | **Alerts Acknowledged**      | Merchant rule                | Alerts a responder has acknowledged in the window - the leading edge of MTTA.                                        |
        | **Alerts Firing**            | Merchant rule                | Alert events raised by Pingdom checks in the window.                                                                 |
        | **Incidents Open**           | Alert band 0 / 3             | Outage windows currently open (down or degraded) across all checks.                                                  |
        | **Incidents Resolved (24h)** | Merchant rule                | Outage windows closed in the last 24 hours - recovery throughput.                                                    |
        | **Mean Time To Acknowledge** | Alert band 300000 / 900000   | Median gap between an incident opening and a responder acknowledging it.                                             |
        | **Mean Time To Resolve**     | Alert band 1800000 / 3600000 | Median gap between an incident opening and being resolved.                                                           |
        | **SLA Compliance**           | Alert band 99.9 / 99.5       | Uptime measured against the SLA target across the window.                                                            |
        | **Services Degraded**        | Alert band 0 / 2             | Checks responding slowly or intermittently but not fully down.                                                       |
        | **Services Down**            | Alert band 0 / 1             | Checks fully unreachable. When the storefront URL is down, join to a commerce sibling to price the outage in \$/min. |
        | **Services Healthy**         | Alert band 1 / 0             | Checks currently reporting an up / healthy state.                                                                    |
        | **Top Alerting Services**    | Merchant rule                | Checks that raised the most alerts in the window - the noisiest / least-stable services.                             |
      </Accordion>

      <Accordion title="Customer experience (6 signals)">
        | Signal                   | Alert behaviour        | What it tracks                                                                         |
        | ------------------------ | ---------------------- | -------------------------------------------------------------------------------------- |
        | **Apdex Score**          | Alert band 0.94 / 0.85 | Satisfied vs tolerating vs frustrated response-time buckets rolled into one 0-1 score. |
        | **Avg Response Time**    | Alert band 200 / 1500  | Average probe response time across all locations.                                      |
        | **Error Rate**           | Alert band 0.5 / 2     | Share of probe checks returning an error / down state.                                 |
        | **Throughput (req/min)** | Alert band 0 / -10     | Probe checks executed per minute across all locations.                                 |
        | **p95 Latency**          | Alert band 800 / 1500  | 95th-percentile probe response time - the slow-tail experience.                        |
        | **p99 Latency**          | Alert band 1500 / 3000 | 99th-percentile probe response time - worst-case slow checks.                          |
      </Accordion>

      <Accordion title="Control risk and change (1 signals)">
        | Signal              | Alert behaviour | What it tracks                                                                                         |
        | ------------------- | --------------- | ------------------------------------------------------------------------------------------------------ |
        | **Top Error Types** | Merchant rule   | Most common probe error reasons (timeout, connection refused, status code, DNS) across failing checks. |
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Audit (4)">
    ### 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.

    <AccordionGroup>
      <Accordion title="Error rate above 2%">
        **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`
      </Accordion>

      <Accordion title="Apdex score below 0.85">
        **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`
      </Accordion>

      <Accordion title="Avg response time above 1500ms">
        **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`
      </Accordion>

      <Accordion title="Throughput dropped > 30% week-over-week">
        **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`
      </Accordion>
    </AccordionGroup>

    #### 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.
  </Tab>

  <Tab title="Automate">
    ### 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 **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=pingdom)

    #### 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.

    <Accordion title="Browse the operations you can build with">
      | 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.
    </Accordion>
  </Tab>
</Tabs>