> ## 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. # Prometheus on Vortex IQ > Monitor Prometheus health, cost and reliability signals, and catch incidents and runaway spend early. Monitor Prometheus 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) | **19** | **4** | **Build your own** | **Ready to build yours** | **12** | | ------------------- | ---------------- | ------------------ | ------------------------ | -------------- | | performance signals | automated checks | automated fixes | workflows | API operations | ## Monitor performance 19 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 | | ----------------------------------- | ----------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | **Revenue at Risk (firing alerts)** | Protect revenue | Merchant rule | Live \$/min loss while critical/warning alerts overlap a commerce sibling's traffic window. Prometheus state becomes a dollar figure. | | **Alerts Acknowledged** | Run operations | Watch only | Firing alerts matched by an active Alertmanager silence - the ack proxy. | | **Alerts Firing** | Control risk and change | Alert band 0 / 3 | Count of alerts in state=firing from /api/v2/alerts. | | **Apdex Score** | Customer experience | Alert band 0.95 / 0.7 | histogram\_quantile-derived satisfaction score from http\_request\_duration\_seconds\_bucket. | | **Avg Response Time** | Customer experience | Alert band 200 / 1000 | rate(http\_request\_duration\_seconds\_sum) / rate(\_count) over the window. | | **Error Rate** | Customer experience | Alert band 0.5 / 2 | rate(http\_requests\_total{code=~"5.."}) / rate(http\_requests\_total). | | **Incidents Open** | Control risk and change | Alert band 0 / 3 | Active (non-suppressed) alert groups from /api/v2/alerts/groups - one group = one incident. | | **Incidents Resolved (24h)** | Run operations | Watch only | Alert groups that transitioned firing→inactive in the last 24h, evaluated from ALERTS series. | | **Mean Time To Acknowledge** | Run operations | Merchant rule | Mean gap between alert activeAt and first matching silence/ack - needs stored alert history. | | **Mean Time To Resolve** | Run operations | Merchant rule | Mean gap between alert activeAt and firing→inactive transition - needs stored alert history. | | **SLA Compliance** | Run operations | Alert band 99.9 / 99.5 | avg\_over\_time(up\[30d]) - uptime ratio expressed as an SLA percentage. | | **Services Degraded** | Control risk and change | Merchant rule | Services breaching p95/error-rate SLO but still up - derived from rules eval + query. | | **Services Down** | Run operations | Alert band 0 / 1 | count(up == 0) by (job) - targets Prometheus can't scrape. | | **Services Healthy** | Run operations | Watch only | count(up == 1) by (job) - targets reporting up across the window. | | **Throughput (req/min)** | Customer experience | Alert band 0 / -10 | sum(rate(http\_requests\_total\[5m])) × 60 - request volume per minute. | | **Top Alerting Services** | Run operations | Watch only | Services ranked by firing-alert count - count by (service) over ALERTS. | | **Top Error Types** | Control risk and change | Watch only | Alertnames ranked by occurrence - count by (alertname) over ALERTS. | | **p95 Latency** | Customer experience | Alert band 200 / 1000 | histogram\_quantile(0.95, sum(rate(http\_request\_duration\_seconds\_bucket\[5m])) by (le)). | | **p99 Latency** | Customer experience | Alert band 200 / 1000 | histogram\_quantile(0.99, ...) - the tail customers feel worst. | ## 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 Prometheus 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 **10 read** and **2 write** operations across silences, alerts, alertgroups, querys, queryranges, rules on Prometheus. 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=prometheus) | Resource | Read operations | Write operations | | ---------------- | --------------- | ---------------- | | silences | 1 | 2 | | alerts | 2 | 0 | | alertgroups | 1 | 0 | | querys | 1 | 0 | | queryranges | 1 | 0 | | rules | 1 | 0 | | series | 1 | 0 | | statusbuildinfos | 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 Prometheus 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.*