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-6edf4b8ea5fb8603fcf25f2438205094@osmc.de
DTSTART;TZID=Europe/Berlin:20261119T161500
DTEND;TZID=Europe/Berlin:20261119T164500
DTSTAMP:20260715T130656Z
CREATED:20260715
LAST-MODIFIED:20260715
PRIORITY:5
SEQUENCE:2
TRANSP:OPAQUE
SUMMARY:Red Hat’s journey of moving Observability for 1000s of clusters to a third party vendor and then back in-house
DESCRIPTION:One of Red Hat’s largest production services, OpenShift Service on AWS with Hosted Control Planes, decided to move their Observability to a third-party vendor a few years ago. This talk gives insights into this journey, looking at the original decision to ditch the in-house Observability service for a proprietary vendor solution, the multi-year experience of running thousands of clusters with them and the final decision to move Observability back in-house, based on 100% open source software. It features technical details about the situation before, during and after using the vendor solution, interesting company-politics and organizational aspects which are important for how and why this adventure occurred. Of course, we’ll also look at costs and at the lessons we learned.\n
URL:https://osmc.de/talks/red-hats-journey-of-moving-observability-for-1000s-of-clusters-to-a-third-party-vendor-and-then-back-in-house/
LOCATION:Ballroom 3
END:VEVENT
END:VCALENDAR