Setup

https://docs.victoriametrics.com/victorialogs/quickstart/
https://docs.victoriametrics.com/victorialogs/cluster/
https://docs.victoriametrics.com/victorialogs/security-and-lb/

install packages:
    victoria-logs binary from official release

directories:
    storage data dir
    config dir
    tls dir if needed

config file:
    systemd unit with command-line flags

users/secrets:
    dedicated service user
    auth credentials / TLS certs outside repo

systemd enable/start/status:
    systemctl enable victorialogs
    systemctl start victorialogs
    systemctl status victorialogs

logs:
    journalctl -u victorialogs
    VictoriaLogs /metrics

victoria-logs-prod \
  -storageDataPath=/var/lib/victoria-logs \
  -httpListenAddr=:9428

local dev:
    use official image or official release binary in a small container

persistent volume:
    mount storageDataPath to a durable volume

security notes:
    do not expose 9428 directly to the internet
    if you need external access, put auth/TLS in front

docker run -d \
  --name victorialogs \
  -p 9428:9428 \
  -v victorialogs-data:/victoria-logs-data \
  docker.io/victoriametrics/victoria-logs:v1.50.0 \
  -storageDataPath=victoria-logs-data

chart options:
    verify whether you are using an official or community chart

values that matter:
    persistence
    service exposure
    auth / ingress
    tls secrets
    resource requests and limits

network policy / service:
    keep query/UI and ingest inside controlled network paths

single-node baseline:
    simple to operate
    easiest way to start

HA pattern:
    replicate collectors to multiple VictoriaLogs instances
    put vmauth in front for query balancing

backup is not HA:
    backup protects data
    HA keeps logs queryable during node loss

rolling restart:
    restart one node at a time if you run multiple instances

upgrade:
    pin version
    test ingestion and query paths after upgrade

useful commands:
    curl /health
    curl /metrics
    curl /select/logsql/query