VictoriaMetrics

#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

There are 2 ways to connect VictoriaMetrics. Follow whichever path matches your deployment; you only need one.

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

1. Confirm your instance URL and type

   Note the base URL of your instance, for example https://vm.internal.example.com, and whether it runs as single or cluster.

2. Submit credentials to Antimetal

   Provide the VictoriaMetrics URL, the Instance Type (single or cluster), and a read-only Bearer Token if the instance is authenticated.

VictoriaMetrics Cloud

Prerequisites

• A VictoriaMetrics Cloud account
• An API key with read access

1. Create a Cloud API key

   In the VictoriaMetrics Cloud console, create an API key with read access.

2. Submit it to Antimetal

   Provide the Cloud API Key in the Antimetal UI. No instance URL is required in Cloud mode.

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