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-b05b64b135c654deacc33cf7c4a8aeb5@osmc.de
DTSTART;TZID=Europe/Berlin:20261118T080000
DTEND;TZID=Europe/Berlin:20261119T180000
DTSTAMP:20260630T115425Z
CREATED:20260630
LAST-MODIFIED:20260630
PRIORITY:5
SEQUENCE:1
TRANSP:OPAQUE
SUMMARY:Monitoring the Unseen: Why Event-Driven APIs Break Traditional Monitoring
DESCRIPTION:(An AsyncAPI Beginner’s Guide)\nMost monitoring tools and mental models are built for request/response systems: you call out, you get an answer, you measure what came back. Event-driven systems — pub/sub, message queues, webhooks, Kafka, MQTT, don’t work that way. A message goes out, zero or a hundred consumers might receive it, and nothing comes back to confirm it worked. When something breaks, there’s often no error, no failed request, no alert. The system just goes quiet. In this talk, I’ll break down exactly where event-driven architectures create blind spots for monitoring: consumer lag, message delivery guarantees, and schema drift between producers and consumers, where a “successful” deployment can quietly break every subscriber downstream without tripping a single alert. Using real AsyncAPI specifications, I’ll walk through a producer/consumer setup, show how schema drift happens in practice, and demonstrate how AsyncAPI’s tooling can validate contracts and surface that drift before it becomes an outage, the same role OpenAPI plays for REST, applied to the part of your stack that doesn’t “respond.” Drawing on my work within the AsyncAPI Initiative, where I contribute to its specification tooling and CLI ecosystem, this talk gives monitoring and infrastructure engineers a practical lens for a part of the system that’s often invisible until it’s already broken. No prior knowledge of event-driven architecture is required.\n
URL:https://osmc.de/talks/monitoring-the-unseen-why-event-driven-apis-break-traditional-monitoring/
END:VEVENT
END:VCALENDAR