Sponsored Session: Salesforce

Sharing of Personal Information with Sponsors In order to facilitate networking and business relationships at the event, you may choose to visit a third partyʼs virtual booth or to access sponsored content. You are never required to visit third party booths or to access sponsored content. When visiting a booth (e.g. by clicking on a third partyʼs logo in the Solutions Showcase or exhibitor directory, and any actions within the booth thereafter including viewing resources), when accessing sponsored sessions in the Sponsor Theater, or by participating in sponsored activities, the third party will receive some of your registration data. This data includes your first name, last name, title, company, address, email, standard demographics questions (i.e. job function, industry), and details about the sponsored content or resources you interacted with. If you choose to interact with a virtual booth or access sponsored content, you are explicitly consenting to receipt and use of such data by the third-party recipients, which will be subject to their own privacy policies.This is an on-demand session and will be available for the duration of the event.Kubernetes cluster’s state is ephemeral in nature and the workloads can run on any nodes or pods. There is a set of great tools available for visualizing “current” state of the cluster. But often times, live site incidents are mitigated and root cause analysis is left for later. This becomes particularly challenging for incidents that happen due to various K8s events since these events are only available for one hour on the cluster. After this, the only way to debug what happened is by correlating various logs and timelines from control plane, hence making it harder to root cause (increases MTRR). Sloop provides a one stop shop solution with a single pane of glass by showing historic view of cluster. In this demo, we will be sharing the top real incidents for which we found the root cause in a matter of minutes using Sloop.