Monitoring & incidents · wired today
What can agents actually do with VictoriaMetrics?
Incidents move faster than humans can tab-switch. The VictoriaMetrics connector is one of 205 executable connectors and gives agents 5 read-only tools, with the credential held in the vault and every call receipted.
The VictoriaMetrics tool list, exactly as agents see it
query— Evaluate a PromQL expression at a single instant and return the matching series with their values (e.g. 'up', 'vm_app_version')query_range— Evaluate a PromQL expression over a time range at a fixed step and return each series as a list of timestamped sampleslabels— List every label name known to this instancelabel_values— List the values a label takes across the series in this instance (use __name__ to list every metric name)tsdb_status— Get TSDB cardinality status: total series, total label/value pairs and top series counts by metric name
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the VictoriaMetrics connector needs
You provide base URL from your VictoriaMetrics account; Quox sends it as a credential embedded in the endpoint path. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: VictoriaMetrics's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running VictoriaMetrics instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.
VictoriaMetrics integration FAQ
What can Quox agents do with VictoriaMetrics?
Agents can run 5 read-only tools against VictoriaMetrics: query, query range, labels, label values, tsdb status. Every call is receipted in the evidence trail.
What does the VictoriaMetrics integration need?
You provide base URL from your VictoriaMetrics account; Quox sends it as a credential embedded in the endpoint path. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my VictoriaMetrics credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the VictoriaMetrics connector?
LIVE-PROVEN: every tool on this page was executed with real credentials against a real running VictoriaMetrics instance (provisioned for the proof, then destroyed), and every call answered successfully. The strongest proof class a connector can carry before it runs inside your own deployment.