I was approached specifically about the talk I'm going to give that the organizers had seen from a meetup recording. It's a special one that gives the audience a chance to participate in crafting the narrative that comes out of the session. It's a choose your own adventure style talk about the pitfalls everyone should avoid with cloud native observability.
I am very excited to share this with platform engineering enthusiasts as they are on the front lines of the pain around providing platforms for their developer organizations, trying to provide observability-first processes, and tackling the challenges that this brings.
Join me on 14 May at 16:30 in the English track hall for the following choose your own adventure style session.
3 Pitfalls Everyone Should Avoid with Cloud Native Observability
Are you looking at your organization’s efforts to enter or expand into the cloud native landscape and feeling a bit daunted by the vast expanse of information surrounding cloud native observability? When you’re moving so fast with agile practices across your DevOps, SRE’s, and platform engineering teams, it’s no wonder this can seem a bit confusing. Unfortunately, the choices being made have a great impact on both your business, your budgets, and the ultimate success of your cloud native initiatives. That hasty decision up front leads to big headaches very quickly down the road.
Join me for an hour of audience engaging power where you the attendee can choose-your-own-pitfalls-adventure, by polling the attendees shall determine the course of the session! I’ll introduce attendees to the problem facing everyone with cloud native observability followed by any 3 common mistakes that I’m seeing organizations make (depending on what the attendees choose!) and how you can avoid them.
I'm very excited to be invited to this platform engineering event and look forward to meeting everyone!
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.