> ## 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. # Incidents Resolved (24h), Grafana > Incidents Resolved (24h) for Grafana stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Metrics type:** [Supporting Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Monitoring](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Incidents Resolved (24h)** is a incidents & alerts metric tracked from Grafana data. It surfaces operational signal at the incidents & alerts layer so merchants can spot regressions, opportunities, and structural patterns in their store performance. The card pairs with sibling metrics in the Incidents & Alerts category to build a complete diagnostic picture; cross-reference the related cards listed below for context. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | Incidents Resolved (24h) as exposed by the Grafana integration. The metric is computed from the latest available data and refreshed on the standard data refresh. | | **Sample type** | Backend API data from Grafana, refreshed on the standard data refresh. | | **Why it matters** | The metric appears in the Incidents & Alerts category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities. | | **Reading the value** | Compare the current period to the prior period to identify direction. Cross-reference siblings for the full diagnostic picture. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `-` | | **Sentiment key** | `gra_incidents_resolved_24h` | | **Roles** | owner, engineering | ## Calculation Calculated automatically from your Grafana data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example *A representative reading of **Incidents Resolved (24h)** for a typical merchant on Grafana.* The card reports the current period value alongside a comparison against the previous period. Direction matters: rising values may be healthy or concerning depending on the underlying metric. Cross-reference the siblings below to triangulate cause when the value moves outside expected range. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | -------------------------------------------------------------------------------- | ----------------------------------------------------- | | [`gra_alerts_acknowledged`](/nerve-centre/kpi-cards/grafana/alerts-acknowledged) | Incidents & Alerts sibling: Alerts Acknowledged. | | [`gra_alerts_firing`](/nerve-centre/kpi-cards/grafana/alerts-firing) | Incidents & Alerts sibling: Alerts Firing. | | [`gra_incidents_open`](/nerve-centre/kpi-cards/grafana/incidents-open) | Incidents & Alerts sibling: Incidents Open. | | [`gra_mtta`](/nerve-centre/kpi-cards/grafana/mean-time-to-acknowledge) | Incidents & Alerts sibling: Mean Time To Acknowledge. | | [`gra_apdex`](/nerve-centre/kpi-cards/grafana/apdex-score) | Performance sibling: Apdex Score. | ## Reconciling against the vendor's own dashboard **Where to look in Grafana's own dashboard:** The Grafana dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ---------------------------------------------------------------------------------------------------------- | --------- | ------------------------ | | **Period boundary.** Vortex IQ uses 30-day rolling by default; vendor dashboards may use calendar periods. | Variable | Match the period range. | | **Time zone.** Vendor uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. | | **Filter scope.** Profile-level filters (channel, B2B, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. | **Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Incidents Resolved (24h) update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard. **Q: Why does my Grafana dashboard show a different number?** The most common reasons are period-boundary differences (Vortex IQ uses 30-day rolling vs vendor's calendar months), time-zone alignment, and filter scope (profile-level vs vendor's all-account view). Match these settings before assuming a real divergence. **Q: How does Incidents Resolved (24h) relate to other incidents & alerts metrics?** Track this card alongside the siblings listed above to build a complete picture. Single-metric reads can mislead; the diagnostic value is in the cross-reference. **Q: Can I customise the alert threshold?** Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default. *** ### Tracked live in Vortex IQ Nerve Centre *Incidents Resolved (24h)* is one of hundreds of KPI pulses Vortex IQ tracks across Grafana and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.