Overview
VictoriaLogs on Cloudzy gives you a fast, self-hosted logs database you control. Spin up a single node for dev or a roomy box for production, then point Vector, Fluent Bit, or syslog at it and start querying in seconds. Dedicated EPYC vCPUs, DDR5 RAM, pure NVMe, and a 10 Gbps uplink keep ingest and queries snappy during peak traffic. Hourly billing means you can scale up for busy hours and dial back down later.
Description
This One-Click image ships VictoriaLogs inside Docker with a lightweight systemd wrapper, plus handy companions like Grafana, Vector, vmauth, vmalert, Alertmanager, and VictoriaMetrics single-node for metrics. VictoriaLogs listens on its native HTTP port and is ready to accept logs and answer queries right away. See the official docs for data model, ingestion methods, and query patterns.
Access the Web Interface
Start by visiting the services already running on your server. Replace <SERVER-IP> with your instance IP.
- VictoriaLogs: http://<SERVER-IP>:9428 (ingestion, queries, and metrics at /metrics).
- Grafana: http://<SERVER-IP>:3000 (first login is admin /admin, then change it).
- VictoriaMetrics single-node: http://<SERVER-IP>:8428 for Prometheus-compatible metrics.
- vmalert UI & API: http://<SERVER-IP>:8880.
- vmauth gateway: http://<SERVER-IP>:8427 for auth and routing.
- Alertmanager: http://<SERVER-IP>:9093.
- Vector API & UI: http://<SERVER-IP>:8686 if enabled in vector config.
Service controls for day-1 operations:
| sudo systemctl start victoria-logs sudo systemctl stop victoria-logs sudo systemctl status victoria-logs docker ps |
Advanced Features
Here are the practical upgrades that matter for a logs database on compute you own. They reduce query latency, keep ingest smooth during spikes, and give you quick rollback if an update misbehaves.
- Dedicated vCPUs and DDR5 RAM to avoid noisy-neighbor stalls on concurrent writes and reads.
- Pure NVMe storage for high IOPS on WAL, index builds, and compactions.
- 10 Gbps network port for high-rate shippers and many dashboard viewers.
- On-demand snapshots and rollback before upgrades or schema changes.
- Hourly billing means staging or load-test clones cost only for the hours you keep them.
A single reboot applies any resize. No data migration or DNS edits needed.
Ease of Use
You get a clean dashboard to power-cycle, snapshot, or migrate regions. Point Vector or Fluent Bit to http://<SERVER-IP>:9428 for HTTP JSON ingestion, or enable syslog receivers on VictoriaLogs if you prefer TCP or UDP 514. Sample recipes are in the docs, and you can keep things simple with default fields and add structure over time.
Performance Focus
If your team is embedding Grafana panels into public status pages or internal portals, lower time to first byte on panels and faster ad hoc queries help pages feel instant. NVMe I/O and a 10 Gbps uplink hold response times steady when multiple users run queries against large windows.
Full Website Control
You have root. Tune retention, prune indexes, configure vmauth users, and wire alerts through vmalert and Alertmanager. The VictoriaLogs container lives under /root/VictoriaLogs, managed by a systemd unit that calls the Makefile targets, so updates are predictable and reversible. Use docker ps to inspect containers, or extend the stack with your own compose files.
Powerful Tools
This image includes or pairs with the following so you can focus on log quality, not scaffolding.
- VictoriaLogs single node for high-speed ingest and query on port 9428.
- Grafana for dashboards and ad-hoc exploration on port 3000.
- VictoriaMetrics single-node when you also want metrics storage on port 8428.
- vmauth to add authentication and route multi-tenant traffic on port 8427.
- vmalert to evaluate alerting rules and expose alert APIs on port 8880.
- Vector as a simple, high-throughput shipper with an API at 8686 when enabled.
Global Reach
Pick the closest region to your users. Cloudzy operates points of presence in:
- North America: New York City, Dallas, Miami, Utah, Las Vegas
- Europe: London, Amsterdam, Frankfurt, Zurich
- Asia-Pacific: Singapore
Each location offers the same 10 Gbps uplink, Tier-1 mix, and 99.95% uptime SLA. The only variable is distance.
Application Details
Version: Not Specified
OS: Ubuntu Server 24.04
Minimum RAM: 1 GB
IP Types: IPv6, IPv4
Deploy VictoriaLogs Now: your logs database and dashboards are ready in minutes.
Notes and references: VictoriaLogs default port 9428 and /metrics endpoint, ingestion examples, and data model are documented by VictoriaMetrics. Default ports for vmauth 8427, vmalert 8880, VictoriaMetrics single-node 8428, and Grafana 3000 with first-login flow are documented in their official guides.
Important: Configuration & Domain Responsibilities
You get full SSH/root access on every OCA. That power also means your changes can break the app. Please read this before tweaking configs.
- You manage the domain. We don’t sell or host domains/DNS. If the app needs a domain, you must point your domain to the server (A/AAAA/CNAME, and MX/TXT if relevant). SSL issuance and many dashboards depend on this being correct.
- Changing the domain/hostname after install isn’t trivial. Many OCAs write the domain into configs (.env, reverse proxy, app URLs). If you change it, also update:
- Reverse proxy (Nginx/Caddy) and TLS certificates
- App “external URL”/base URL and callback/webhook URLs
- Any hard-coded links in the app or add-ons
- Credentials matter. Renaming the default admin, rotating passwords, or changing service ports without updating the app config can lock you out or stop services. Keep credentials safe and in sync across the app, proxy, and any integrations.
- Nameserver changes can cause downtime. Moving your domain to new nameservers or editing NS records triggers propagation delays. Plan changes, lower TTL ahead of time, and verify A/AAAA records before switching.
- Firewall/port edits can break access. If you change SSH, HTTP/HTTPS, RDP, or app ports, update firewalls (UFW/CSF/security groups) and reverse-proxy rules accordingly.
- Email (SMTP) ports are restricted by default. Outbound mail ports (e.g., 25/465/587) may be closed to prevent abuse. If your OCA must send email, request SMTP access. from support or use a transactional email provider (SendGrid/Mailgun/SES) via API or approved SMTP.
- Email & allowlists. If the app sends mail or receives webhooks, changing IPs/hostnames may affect deliverability or allowlists. Update SPF/DKIM/DMARC and any IP allowlists.
- Before any big change: take a snapshot. Use the panel’s snapshot/backup first. If a plugin, update, or config edit backfires, you can roll back in minutes.
- Support scope. We provide the server and the preinstalled OCA image. Ongoing application-level configuration (domains, DNS, app settings, plugins, and custom code) is the user’s responsibility.
Quick rule of thumb: if you touch domain, ports, passwords, hostnames, or proxy/SSL configs, expect to update the app’s settings too, and snapshot first.
Installation
- Cloned VictoriaMetrics repo from GitHub to
/root/VictoriaLogs - Installed Docker and dependencies
- Created systemd service
victoria-logsto manage VictoriaLogs container via make commands
Commands
sudo systemctl start victoria-logs # Start VictoriaLogs service sudo systemctl stop victoria-logs # Stop service sudo systemctl status victoria-logs # Check service status docker ps # List running Docker containers
Access URLs
- Single-node VictoriaLogs →
http://<SERVER-IP>:9428 - Grafana →
http://<SERVER-IP>:3000 - Single-node VictoriaMetrics →
http://<SERVER-IP>:8428 - vmalert →
http://<SERVER-IP>:8880 - vmauth →
http://<SERVER-IP>:8427 - Alertmanager →
http://<SERVER-IP>:9093 - Vector UI →
http://<SERVER-IP>:8686
Documentation
- https://docs.victoriametrics.com/victorialogs/