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-925cdef65f6a1d131fd8ca6c867c5c0a@osmc.de
DTSTART;TZID=Europe/Berlin:20261118T111500
DTEND;TZID=Europe/Berlin:20261118T120000
DTSTAMP:20260709T132733Z
CREATED:20260709
LAST-MODIFIED:20260715
PRIORITY:5
SEQUENCE:4
TRANSP:OPAQUE
SUMMARY:Evolution, Not Revolution: Growing Observability on Top of the Monitoring You Already Have
DESCRIPTION:It’s 2 a.m. Your monitoring is doing exactly what you built it to do: a check has gone red, the alert fired, you know something is wrong. So you start digging, and that’s where it gets slow. Which request? Which dependency? Why this time and not the last thousand? Your checks and dashboards told you that there’s a problem. Answering why is a different job, and it’s the job traces and logs are built for. You’ve spent years building your monitoring, Icinga, Nagios, Checkmk, dashboards, a log pipeline, and it works. Now everyone’s talking about “observability” and OpenTelemetry, and the unspoken question is: do I throw this away and start over?\nYou don’t. This talk argues the move is evolution, not revolution. The real shift isn’t a new tool that replaces your monitoring, it’s getting the signals you already collect to work as one story instead of three. Most of you already have metrics, checks, and logs. The signal that completes the picture is tracing — the end-to-end view of a request, valuable even in a monolith and it’s easy to add with zero-code auto-instrumentation.\nBut adding a signal isn’t the point; connecting them is. In a live demo we’ll take a metric spike, a trace, and a log line and watch them come together into a single investigation, linked by shared context, feeding an open-source backend that runs alongside the tools you already operate.\nYou’ll leave with a concrete, low-risk path to make the monitoring you already trust answer “why,” not just “what.”\n
URL:https://osmc.de/talks/evolution-not-revolution-growing-observability-on-top-of-the-monitoring-you-already-have/
LOCATION:Ballroom 3
END:VEVENT
END:VCALENDAR