Skip to main content

​
Overview

This guide walks you through connecting a VictoriaLogs instance to Antimetal. Antimetal runs a dedicated read-only connector that queries your instance using LogsQL.

Set up in Antimetal

Go to the Victoria Logs integration setup in the Antimetal dashboard.
VictoriaLogs is self-hosted only today (Cloud support is on the VictoriaMetrics roadmap). It usually lives inside your own network, so before connecting, review Self-Hosted Observability to make it reachable by Antimetal.

​
Prerequisites

  • A running VictoriaLogs instance, reachable over HTTPS from Antimetal
  • A read-only bearer token if your instance requires authentication

​
Setup

1

Confirm your instance URL

Note the base URL of your VictoriaLogs instance, for example https://vmlogs.internal.example.com.
2

Create a read-only token (if applicable)

If your instance is protected, provision a bearer token scoped to read-only query access.
3

Submit credentials to Antimetal

FieldValue
VictoriaLogs URLThe base URL of your instance
Bearer TokenRead-only token (optional if the instance is unauthenticated)

​
Permissions and Access

Antimetal uses a read-only connector restricted to query and exploration tools (query, hits, facets, field and stream listings, and stats_query). VictoriaLogs exposes no write or ingestion tools, and none are enabled.