BEGIN:VCALENDAR
VERSION:2.0
METHOD:PUBLISH
CALSCALE:GREGORIAN
PRODID:-//WordPress - MECv7.28.0//EN
X-ORIGINAL-URL:https://osmc.de/
X-WR-CALNAME:OSMC
X-WR-CALDESC:Open Source Monitoring Conference
X-WR-TIMEZONE:Europe/Berlin
BEGIN:VTIMEZONE
TZID:Europe/Berlin
X-LIC-LOCATION:Europe/Berlin
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:20260329T030000
RRULE:FREQ=YEARLY;BYMONTH=03;BYDAY=-1SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:20261025T020000
RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=4SU
END:STANDARD
END:VTIMEZONE
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-PUBLISHED-TTL:PT1H
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VEVENT
CLASS:PUBLIC
UID:MEC-762f942f9ebc76e485a774e4bea7f4de@osmc.de
DTSTART;TZID=Europe/Berlin:20261118T140000
DTEND;TZID=Europe/Berlin:20261118T143000
DTSTAMP:20260708T143515Z
CREATED:20260708
LAST-MODIFIED:20260715
PRIORITY:5
SEQUENCE:2
TRANSP:OPAQUE
SUMMARY:Vector and VictoriaLogs: Powerhouse combo for Database logging Observability
DESCRIPTION:Any troubleshooting where a DBA is involved, reading and analysing DB log entries is a must. Database logfiles are like a weapon in production environment. Not only reactively but also proactively monitoring database log files is crucial. But it is not as common as it should be. It becomes particularly a challenge in environments with thousands of very highly active databases generating massive amount of log data. 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) is not very practical and efficient. Hence, the need for a better approach. In my talk, I will be presenting a solution for DB logging Observability: Vector + Victoria Logs.\n
URL:https://osmc.de/talks/vector-and-victorialogs-powerhouse-combo-for-database-logging-observability/
LOCATION:Ballroom 1+2
END:VEVENT
END:VCALENDAR