logyard_vector_deploy¶

Deploys Vector on a producer host and ships journald logs to Logyard/Loki.

Features¶

installs Vector from the official apt repository
reads from journald first
normalizes logs into a compact JSON payload
keeps Loki labels low-cardinality and stable
uses disk buffering and explicit retry settings
disables Vector’s Loki sink startup health check by default so transient Logyard/Loki errors do not prevent the producer from booting; runtime delivery still uses retries and disk buffering
writes a shared Vector config directory under /etc/vector/config.d/
stores the Logyard pipeline in its own fragment so it can coexist with other Vector-managed services on the same host
validates the full staged config directory before replacing the live fragment

Required Variables¶

logyard_vector_enabled: true
logyard_vector_ingest_endpoint: "https://logyard.home.xn--wersdrfer-47a.de"

Default Label Set¶

The sink labels are:

host
service
source_type
environment
level

unit, pid, and syslog_identifier stay in the JSON log payload instead of the Loki index.

Common Variables¶

logyard_vector_host_id: "macmini"
logyard_vector_environment: "prod"
logyard_vector_source_type: "journald"
logyard_vector_include_units: []
logyard_vector_exclude_units: []
logyard_vector_current_boot_only: false
logyard_vector_healthcheck_enabled: false

Example Playbook¶

- hosts: macmini
  become: true
  roles:
    - role: local.ops_library.logyard_vector_deploy
      vars:
        logyard_vector_enabled: true
        logyard_vector_ingest_endpoint: "https://logyard.home.xn--wersdrfer-47a.de"
        logyard_vector_host_id: "macmini"
        logyard_vector_environment: "prod"

Validation¶

systemctl status vector
journalctl -u vector -n 100 --no-pager
vector validate --config-dir /etc/vector/config.d
ls /etc/vector/config.d

Use vector validate --skip-healthchecks --config-dir /etc/vector/config.d when checking producer config syntax/topology without requiring the remote Logyard/Loki endpoint to be healthy at that moment.