PostgreSQL Conference Germany 2026

Any troubleshooting where a DBA is involved, reading and analysing DB log entries is a must. Database logfiles are a DBA’s weapon in production environment. Not only reactively but also proactively monitoring database log files is crucial. However, in environments with thousands of very highly active databases generating massive amount of logging and compliance policies to abide by, analysing a single log file by manually browsing through it either by logging into the DB server or by downloading the file to a local machine to create some reports( that takes resource and time for processing and producing some basic views/aggregates) is not very practical and efficient. Hence, the need for a better approach.

In my talk, I will be presenting an alternative solution for DB logging Observability solution : Vector + Victoria Logs.

Vector: Reads, transforms and ships the log file to different targets VictoriaLogs: VictoriaLogs is a storage for logs and uses LogsQL for querying and create statistical data from the log files Both Vector and Victorialogs are open source

The Agenda would include:

Traditional approach New Requirement New solution Old vs new Log configurations What is vector? Vector vs Promtail What is VictoriaLogs? VictoriaLogs vs Loki LogsQL: Introduction and examples Grafana Dashboards with VictoriaLogs as source using LogsQL for metrics My experience : Pros, cons and why this was a chosen solution