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-08648e60ac32d2c805ab6b0e0c174180@osmc.de
DTSTART;TZID=Europe/Berlin:20261118T080000
DTEND;TZID=Europe/Berlin:20261119T180000
DTSTAMP:20260629T125656Z
CREATED:20260629
LAST-MODIFIED:20260629
PRIORITY:5
SEQUENCE:1
TRANSP:OPAQUE
SUMMARY:Capability-as-a-Service: Self-Hosted Observability That Feels Like SaaS
DESCRIPTION:Ask a platform team what they want from observability and the answer is simple: it should just be there, like any SaaS. Build it on open source, though, and you are suddenly running eight separate projects, each one a job of its own to operate. We have made that kind of operational pain disappear before, one tool at a time, with Kubernetes operators. But observability is not one tool, it is a capability made of many, and no single operator covers the work of turning that pile into one coherent service. So, what does it actually take to get the SaaS feeling from self-hosted OSS? Building on that same operator model, I share a pattern we call Capability-as-a-Service, and the open-source reference implementation we built to prove it works. This is for platform engineers and SREs who run their own observability and want it to feel bought while staying theirs.\n
URL:https://osmc.de/talks/capability-as-a-service-self-hosted-observability-that-feels-like-saas/
END:VEVENT
END:VCALENDAR