Skip to main content

​
Overview

This guide walks you through connecting VictoriaMetrics to Antimetal. Antimetal runs a dedicated read-only connector that queries your instance using PromQL and MetricsQL.

Set up in Antimetal

Go to the Victoria Metrics integration setup in the Antimetal dashboard.

​
Setup

Choose the tab that matches your deployment.
A self-hosted instance usually lives inside your own network. Before connecting, review Self-Hosted Observability to make it reachable by Antimetal.

​
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

FieldValue
VictoriaMetrics URLThe base URL of your instance
Instance Typesingle or cluster
Bearer TokenRead-only token (optional if the instance is unauthenticated)
VictoriaMetrics is Prometheus-compatible, so existing Prometheus queries work directly.

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