VictoriaMetrics
VictoriaMetrics is a Prometheus-compatible time series database, so existing Prometheus queries work against it directly. Antimetal runs a dedicated read-only connector that queries your instance using PromQL and MetricsQL.
What Antimetal does with VictoriaMetrics
- Run PromQL and MetricsQL queries, both instant and over a range
- Inspect labels and series to find the dimension that changed
- Read alerting and recording rules, and current alert state
- Check TSDB status to understand cardinality and ingestion health
Connecting VictoriaMetrics
Self-hosted
A self-hosted instance usually lives inside your own network. Review the self-hosted reachability options below before connecting.
Prerequisites
- A running VictoriaMetrics instance, reachable over HTTPS from Antimetal
- Whether your deployment is single-node or cluster
- A read-only bearer token if your instance requires authentication
Note the base URL of your instance, for example
https://vm.internal.example.com, and whether it runs assingleorcluster.Provide the VictoriaMetrics URL, the Instance Type (
singleorcluster), and a read-only Bearer Token if the instance is authenticated.
VictoriaMetrics Cloud
Prerequisites
- A VictoriaMetrics Cloud account
- An API key with read access
In the VictoriaMetrics Cloud console, create an API key with read access.
Provide the Cloud API Key in the Antimetal UI. No instance URL is required in Cloud mode.
Follow whichever path matches your deployment — you only need one.
Permissions and access
Antimetal uses a read-only connector restricted to query and inspection tools — query, query_range, labels, series, rules, alerts, TSDB status, and, in Cloud, deployment and region inspection. No write operations are performed.
All tenant data is processed in isolated environments. See security and compliance for details.
Related integrations
Need help?
Contact us via Slack or at support@antimetal.com.