VictoriaLogs on Ubuntu 24.04 LTS

This is a repackaged open source software product wherein additional charges apply for cloudimg support services.

VictoriaLogs - Fast, Cost Efficient Log Database, by cloudimg

Deploy a private, self-hosted log database on your own Azure infrastructure in minutes - no manual installation, no default credentials, no third-party service. This image delivers VictoriaLogs 1.52.0 fully installed, hardened, and reverse-proxied behind nginx, so your team can ship logs and run queries immediately after the VM boots.

Why This Image Instead of Manual Installation

Installing VictoriaLogs by hand means placing the server binary, writing a systemd unit, configuring an nginx reverse proxy with an authentication gate, laying out storage, and generating credentials. This image eliminates that operational burden:

• Pre-configured nginx reverse proxy with HTTP Basic Auth in front of the loopback-bound server
• Secure by default: a unique password is generated on the first boot of every VM, so no default login ever ships
• Immediate time-to-value: ship logs and run LogsQL queries within minutes of the VM starting
• Ongoing expert support: 24/7 cloudimg engineers handle upgrades, storage migration, reverse proxy and TLS termination

Use Case: Self-Hosted Log Management Without a Heavy Stack

Teams want to collect, store and search their application and infrastructure logs without running a heavy Elasticsearch or Loki stack or sending logs to a third-party service. With this image they launch a VM and immediately point their log shippers at it, then search and analyse the results with LogsQL through the built-in web UI, all within their own VNet with full control of the data.

Application Stack

VictoriaLogs is a single self-contained Go binary. It serves its web UI (vmui) and HTTP ingestion and query APIs on the loopback interface (127.0.0.1:9428), fronted by nginx as a reverse proxy on port 80 with a per-VM HTTP Basic Auth gate. All log data lives on a dedicated Azure data disk, separate from the operating system disk and re-provisioned with every VM, with a 30 day default retention you can tune.

Secure By Default

VictoriaLogs has no built-in authentication. Rather than exposing it directly, this image binds it to loopback and puts an nginx HTTP Basic Auth gate in front, then generates a unique password on the first boot of every VM and records it in a protected file readable only by root, so no shared or default credential is baked in. An unauthenticated health endpoint is provided for load balancer probes.

Features

Ingest logs over the JSON stream, Loki push, Elasticsearch bulk, OpenTelemetry and syslog protocols; store them compactly on disk; and search and analyse them with the LogsQL query language through the vmui web interface or the HTTP query API. View results grouped, as a table, or as structured JSON, with a hits histogram over time.

Getting Started

1. Launch the image on your chosen Azure VM size 2. Read the per-VM password from /root/victorialogs-credentials.txt 3. Browse to the VM public IP at /select/vmui/ and sign in as admin to explore your logs 4. Point your log shippers at the /insert APIs using the same credentials

Licensing and Pricing

VictoriaLogs is licensed under Apache-2.0 and is free; there is no per-seat or per-gigabyte fee. The cloudimg charge of 0.04 US dollars per vCPU hour covers packaging, security patching, image maintenance, and 24/7 expert support. VictoriaLogs serves plain HTTP on port 80; terminate TLS in front of it with your own domain before production.

cloudimg Support

24/7 technical support by email covers deployment, upgrades, storage migration, reverse proxy configuration, and TLS termination. Critical issues receive a one-hour average response time.

VictoriaLogs and VictoriaMetrics are trademarks of their respective owners. This image is provided by cloudimg and is not affiliated with, endorsed by, or sponsored by VictoriaMetrics. Use of the names does not imply any affiliation with or endorsement by them.