Overview
This guide walks you through connecting VictoriaMetrics to Opriven. Opriven runs a dedicated read-only connector that queries your instance using PromQL and MetricsQL.
Set up in Opriven
Go to the Victoria Metrics integration setup in the Opriven dashboard.
Setup
Choose the tab that matches your deployment.
Self-Hosted
VictoriaMetrics Cloud
A self-hosted instance usually lives inside your own network. Before connecting, review
Self-Hosted Observability
to make it reachable by Opriven.
Prerequisites
A running VictoriaMetrics instance, reachable over HTTPS from Opriven
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 Opriven
Field
Value
VictoriaMetrics URL
The base URL of your instance
Instance Type
single
or
cluster
Bearer Token
Read-only token (optional if the instance is unauthenticated)
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 Opriven
Provide the
Cloud API Key
in the Opriven UI. No instance URL is required in Cloud mode.
VictoriaMetrics is Prometheus-compatible, so existing Prometheus queries work directly.
Permissions and Access
Opriven 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.