Files
configpolicy/group_vars/victoria-logs.yml
Dustin C. Hatch f1b61a8d0a v-l: Enable useRemoteIP for syslog
Victoria Logs can now record the source address for syslog messages in a
`remoteIP` field.  This has to be enabled specifically, although I can't
think of a reason why someone would _not_ want to record that
information.
2025-11-24 07:47:35 -06:00

50 lines
1.6 KiB
YAML

data_volumes:
- dev: /dev/vdb
fstype: ext4
mountpoint: /var/lib/victoria-logs
victoria_logs_extra_args:
- '-syslog.listenAddr.tcp=:601'
- '-syslog.useRemoteIP.tcp=true'
- '-syslog.listenAddr.udp=:514'
- '-syslog.useRemoteIP.udp=true'
- '-syslog.extraFields.udp=''{}'''
- '-syslog.streamFields.udp=''["hostname","app_name","proc_id"]'''
- '-syslog.listenAddr.udp=:6666'
- '-syslog.extraFields.udp=''{"stream":"netconsole"}'''
- '-syslog.streamFields.udp=''["stream"]'''
victoria_logs_publish_ports:
- '514:514/udp'
- '601:601'
#- '6514:6514'
- '6666:6666/udp'
victoria_logs_firewall_ports:
- 514/udp
- 601/tcp
#- 6514/tcp
- 6666/udp
victoria_logs_caddy_server_name: logs.pyrocufflink.blue
victoria_logs_tls_client_auth: true
victoria_logs_tls_ca_cert: |+
-----BEGIN CERTIFICATE-----
MIIBlDCCAUagAwIBAgIUGNZ/ASP8F2ytev3YplTk4jA5a2EwBQYDK2VwMEgxCzAJ
BgNVBAYTAlVTMRgwFgYDVQQKDA9EdXN0aW4gQy4gSGF0Y2gxDTALBgNVBAsMBExv
a2kxEDAOBgNVBAMMB0xva2kgQ0EwHhcNMjQwMjIwMTUwMTQxWhcNMzQwMjIwMTUw
MTQxWjBIMQswCQYDVQQGEwJVUzEYMBYGA1UECgwPRHVzdGluIEMuIEhhdGNoMQ0w
CwYDVQQLDARMb2tpMRAwDgYDVQQDDAdMb2tpIENBMCowBQYDK2VwAyEAnmMawEIo
WfzFaLgpSiaPD+DHg28NHknMFcs7XpyTM9CjQjBAMB0GA1UdDgQWBBTFth3c4S/f
y0BphQy9SucnKN2pLzASBgNVHRMBAf8ECDAGAQH/AgEAMAsGA1UdDwQEAwIBBjAF
BgMrZXADQQCn0JWERsXdJA4kMM45ZXhVgAciwLNQ8ikoucsJcbWBp7bSMjcMVi51
I+slotQvQES/vfqp/zZFNl7KKyeeQ0sD
-----END CERTIFICATE-----
victoria_logs_caddy_forward_auth:
url: https://auth.pyrocufflink.blue
path: /api/verify
location: '?rd={scheme}://{host}{uri}'
victoria_logs_caddy_acme:
email: victoria_logs@pyrocufflink.blue
url: https://ca.pyrocufflink.blue/acme/acme/directory