Catalog / Databases & caches

VictoriaMetrics

Time-series database and Prometheus-compatible monitoring backend

CIS Level 1 hardened Ubuntu 24.04 LTS image by Lynxroute · unique credentials at first boot · CVE-scanned · SBOM and CIS report inside

Availability and pricing
CloudVersionSoftware priceLast build
Azure Marketplace
VM image · plan payg-gen2 · Gen2
1.153.0$0.028/vCPU/hr
Recommended VM: Standard_D2s_v3
2026-10-02Listing ↗

Software price only; cloud infrastructure is billed separately by the provider. Prices in USD.

Image facts
Base OSUbuntu 24.04 LTS
HardeningCIS Level 1, Ubuntu 24.04 LTS (tailored)
LicenseApache-2.0
UpstreamVictoriaMetrics
Machine-readableproduct.json · catalog.json
What is VictoriaMetrics

VictoriaMetrics is a Go-based, single-binary time-series database and monitoring solution designed for high performance and low resource usage. It speaks the Prometheus ecosystem natively: ingest metrics via Prometheus remote_write, the InfluxDB line protocol, Graphite, OpenTSDB, CSV, or its JSON import API, and query them back with PromQL or the more expressive MetricsQL through a Prometheus-compatible HTTP API. A built-in web UI (vmui) lets you explore and graph metrics straight from the browser. This is the single-node edition: one self-contained process that stores samples in its own on-disk TSDB, so there is nothing else to operate. Data is kept with a 12-month retention window by default on a dedicated data path. The community edition is Apache-2.0, so the whole stack is auditable with no vendor lock-in, and running it in your own AWS account keeps all metrics inside your boundary.

What the Lynxroute image adds

Security hardening:

  • VictoriaMetrics (port 8428) bound to localhost only - never exposed directly
  • Nginx reverse proxy with TLS on port 443 in front of the HTTP API and vmui
  • HTTP Basic Auth perimeter with a unique credential generated at first launch (single-node VictoriaMetrics has no built-in auth)
  • Community single-node build only - the enterprise build is never downloaded or shipped (verified by a build-time assertion)
  • certbot and the Nginx plugin pre-installed for one-command CA-signed HTTPS
  • UFW firewall - ports 22, 80, 443 only
  • fail2ban, AppArmor
  • CVE scan - every image is scanned for vulnerabilities before release

OS hardening (CIS Level 1):

  • CIS Ubuntu 24.04 LTS Level 1 benchmark applied via ansible-lockdown
  • auditd, SSH hardening, Kernel hardening, IMDSv2 enforced

Compliance artifacts:

  • SBOM - CycloneDX 1.6 at /etc/lynxroute/sbom.json
  • CIS Conformance Report at /etc/lynxroute/cis-report.html
  • CIS Tailored Profile at /usr/share/doc/lynxroute/CIS_TAILORED_PROFILE.md
Deploy

Launch in one command

Credentials are generated at first boot and written to /root/victoriametrics-credentials.txt.

# accept the plan terms once, then:
az vm image terms accept --publisher lynxroute --offer victoriametrics --plan payg-gen2
az vm create -g my-rg -n victoriametrics --size Standard_D2s_v3 \
  --image lynxroute:victoriametrics:payg-gen2:latest --admin-username azureuser --generate-ssh-keys
Release notes

Latest release

The most recent release with notes; the full release history is in product.json.

VictoriaMetrics 1.153.0

Azure · 2026-10-02
  • VictoriaMetrics single-node updated 1.152.0 -> 1.153.0. Apache-2.0 unchanged
  • Security: memory limits are now applied to zstd-encoded blocks ingested via native import, preventing excessive memory allocation from crafted requests
  • Service-discovery scrape targets are now dropped when a *_sd_config returns an empty target list, instead of being kept until restart
  • Opt-in random-read hints for data part files can reduce disk I/O and improve page cache efficiency
  • Slightly lower CPU usage during concurrent queries; the vmui auto-refresh controls move to the Execute button
  • Rebuilt on the current CIS Level 1 hardened Ubuntu 24.04 LTS base to pick up the latest Ubuntu security updates