Skip to main content
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.
The VictoriaMetrics stack is connected through Grafana: connect Grafana, and Nexus discovers the data sources behind it automatically, using Grafana’s own credentials.

​
What we support

​
Connecting VictoriaMetrics

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

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

Grafana

The provider the VictoriaMetrics stack is connected through.

How telemetry works

How Nexus queries your telemetry.