VictoriaLogs

#What Antimetal does with VictoriaLogs

• Query logs with LogsQL across the window around an alert
• Use hits and facets to find which fields separate failing requests from healthy ones
• List fields and streams to learn the shape of your log data
• Run stats queries to quantify how much and how fast something changed

#Connecting VictoriaLogs

VictoriaLogs is self-hosted only today — Cloud support is on the VictoriaMetrics roadmap. It usually lives inside your own network, so review the self-hosted reachability options below before connecting.

Prerequisites

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

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

   Provide the VictoriaLogs URL and, if your instance is authenticated, the read-only Bearer Token.

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

All tenant data is processed in isolated environments. See security and compliance for details.