> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# VictoriaMetrics

> Query your VictoriaMetrics metrics, logs, and traces to see what your services were doing during an incident.

The VictoriaMetrics stack stores metrics in VictoriaMetrics, logs in VictoriaLogs, and traces in VictoriaTraces. Nexus queries all three to see what your services were doing around the time of an incident.

<Note>
  The VictoriaMetrics stack is connected through [Grafana](/nexus/telemetry/grafana): connect Grafana, and Nexus
  discovers the data sources behind it automatically, using Grafana's own credentials.
</Note>

## What we support

| Product | What Nexus queries |
| - | - |
| VictoriaMetrics | Metrics, with PromQL, the same way it queries [Prometheus](/nexus/telemetry/prometheus): rates from counters, percentiles from histograms |
| VictoriaLogs | Logs, with LogsQL: what your services logged around the incident, and counts over them, such as errors per service or how often a message appeared minute by minute |
| VictoriaTraces | Traces, the same way it queries [Tempo](/nexus/telemetry/tempo): searching spans and looking up a trace by ID |

## Connecting VictoriaMetrics

Connect [Grafana](/nexus/telemetry/grafana) with a data source for each product you run:

* **VictoriaMetrics**: a **Prometheus** data source pointed at VictoriaMetrics. Nexus discovers Prometheus data sources rather than ones built on the VictoriaMetrics plugin for Grafana, so if your Grafana only has the plugin, add a Prometheus data source pointed at the same URL.
* **VictoriaLogs**: a **VictoriaLogs** data source, from the VictoriaLogs plugin for Grafana.
* **VictoriaTraces**: a **Tempo** data source pointed at VictoriaTraces.

Make sure the Grafana service account can query each of them.

Discovered data sources start disabled, so you opt in deliberately: enable the ones your team uses from your [telemetry settings](https://app.incident.io/~/nexus/telemetry).

## Best practice

* Connect the Grafana dashboards that query your VictoriaMetrics stack. Nexus learns your real query patterns from them, which makes its queries more accurate.
* Enable the data sources your responders reach for during incidents, rather than every source available.

## Related

<CardGroup cols={2}>
  <Card title="Grafana" icon="database" href="/nexus/telemetry/grafana">
    The provider the VictoriaMetrics stack is connected through.
  </Card>

  <Card title="How telemetry works" icon="magnifying-glass" href="/nexus/telemetry/how-it-works">
    How Nexus queries your telemetry.
  </Card>
</CardGroup>