VM-side Vector rollout: ship host logs to the central logging stack #500
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The centralized logging platform (Vector→JetStream→ClickHouse) is live for k8s, and Tier-1/Tier-2 transforms for VM apps (nginx, HAProxy, glauth, BIND, puppetserver, postfix, Vault file-audit) are implemented but dormant — nothing on the ~143-VM fleet ships logs yet, and the transforms match on
.file/.SYSLOG_IDENTIFIERsource tags the VMs must set.Proposal
https://logs-ingest.k8s.syd1.au.unkin.net(vector-native/HTTPS), publishing tologs.vm.<host>subjects.fileon file sources,.SYSLOG_IDENTIFIERon journald, for named/nginx/haproxy/glauth/postfix/puppetserver/vault_auditquerylog yesinprofiles/dns/server.pppuppetserver-access.logAcceptance
logs.rawunderlogs.vm.*; the dormant Tier-1/2 transforms populate structured fields;SELECT count() FROM logs.raw WHERE ...vm...rising; Vault file-audit reaches the logarchiver archive subject.