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

# Grafana on Vortex IQ

> Monitor Grafana health, cost and reliability signals, and catch incidents and runaway spend early.

Monitor Grafana 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** | **9**          |
| ------------------- | ---------------- | ------------------ | ------------------------ | -------------- |
| 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 × Revenue at Risk** | Protect revenue         | Alert band 0 / 1             | Down services joined to a commerce sibling's revenue/min baseline - turns 'a service is down' into '\$/min on fire'. |
| **Alerts Firing**                   | Run operations          | Alert band 0 / 5             | Grafana-managed alert instances currently in the Alerting state.                                                     |
| **Apdex Score**                     | Customer experience     | Alert band 0.94 / 0.85       | Apdex(t) computed from request-duration histogram in PromQL - good below 0.85 is unacceptable.                       |
| **Error Rate**                      | Customer experience     | Alert band 0.5 / 2           | 5xx / errored requests as a share of total, from PromQL via the data-source proxy.                                   |
| **Mean Time To Acknowledge**        | Run operations          | Alert band 300000 / 1800000  | Mean elapsed time from incident creation to first acknowledgement - gated on the Grafana Incident plan.              |
| **Throughput (req/min)**            | Customer experience     | Alert band 0 / -30           | Throughput (req/min) over time.                                                                                      |
| **Top Alerting Services**           | Run operations          | Alert band 0 / 5             | Services ranked by firing-alert count over the window - where the noise concentrates.                                |
| **Top Error Types**                 | Control risk and change | Alert band 0 / 5             | Error classes ranked by count via LogQL/PromQL through the data-source proxy.                                        |
| **Alerts Acknowledged**             | Run operations          | Alert band 0 / 5             | Description pending editorial review; the signal is live.                                                            |
| **Avg Response Time**               | Customer experience     | Alert band 200 / 1000        | Description pending editorial review; the signal is live.                                                            |
| **Incidents Open**                  | Run operations          | Alert band 0 / 3             | Description pending editorial review; the signal is live.                                                            |
| **Incidents Resolved (24h)**        | Run operations          | Alert band 0 / -1            | Description pending editorial review; the signal is live.                                                            |
| **Mean Time To Resolve**            | Run operations          | Alert band 1800000 / 3600000 | Description pending editorial review; the signal is live.                                                            |
| **SLA Compliance**                  | Run operations          | Alert band 99.9 / 99.5       | Description pending editorial review; the signal is live.                                                            |
| **Services Degraded**               | Run operations          | Alert band 0 / 2             | Description pending editorial review; the signal is live.                                                            |
| **Services Healthy**                | Run operations          | Alert band 0 / -1            | Description pending editorial review; the signal is live.                                                            |
| **p95 Latency**                     | Customer experience     | Alert band 800 / 1500        | Description pending editorial review; the signal is live.                                                            |
| **p99 Latency**                     | Customer experience     | Alert band 1500 / 3000       | 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 Grafana 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 **8 read** and **1 write** operations across alertmanagergrafanaalerts, alertmanagergrafanaalertgroups, dquerys, datasources, incidents, prometheugrafanarules on Grafana. 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=grafana)

<Accordion title="Browse the operations you can build with">
  | Resource                       | Read operations | Write operations |
  | ------------------------------ | --------------- | ---------------- |
  | alertmanagergrafanaalerts      | 1               | 0                |
  | alertmanagergrafanaalertgroups | 1               | 0                |
  | dquerys                        | 0               | 1                |
  | datasources                    | 1               | 0                |
  | incidents                      | 1               | 0                |
  | prometheugrafanarules          | 1               | 0                |
  | provisioningalertrules         | 1               | 0                |
  | searchs                        | 1               | 0                |

  Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.
</Accordion>

### Ready to build your first Grafana 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.*
