Operations | Monitoring | ITSM | DevOps | Cloud

Try it open source on your system. Learn how tools can make gathering and making sense of observability data instant and painless with co-founder Peter Zaitsev.

All the problems that could go wrong with DNS and why "It's always a Freaking DNS Issue" according to DevOps movement co-founder and open source advocate Kris Buytaert.

Learn what DevOps is from a founder of the movement, Co-founder of DevOpsDays, O11y, and Inuits, FOSS advocate: Kris Buytaert.

Understand the four pillars of observability (metrics, logs, traces, and profiles) with Co-founder Peter Zaitsev.

Alex chats with Kris Buytaert, Co-founder of DevOpsDays, O11y, Inuits and pivotal instigator of the movement about why he loves using Coroot.

Kris Buytaert is the Co-founder of Inuits, O11y, and ‘DevOps Days,’ an internationally-attended series of DevOps events. He is a passionate advocate of Free and Open Source Software, and is accredited by the community as being a founding instigator of the DevOps movement. In this episode we trace the history of the DevOps movement from its intersection with open source and Agile, through the evolution of Cloud technologies and tools such Docker and Kubernetes, to present day best practices for CI/CD, monitoring, and observability.

Co-founder of DevOps Days, O11y, Inuits, and pivotal instigator of the DevOps movement Kris Buytaert explains why “observability best practices” starts with functioning monitoring and common mistakes to avoid.

Watch Coroot’s Root Cause Analysis AI pinpoint the exact cause of an incident and suggest fixes in seconds.

🐧🐝 Learn what classic CPU metrics are (Load average, Node usage, and Container CPU usage) and why Delay Accounting can provide better, kernel-level insights into your system: https://t.ly/HQrWx

#DevOps #Kubernetes #AI #tech #observability #Linux #eBPF #Sysadmin #Cloud #Monitoring

Incidents can quickly become costly, and digging through overwhelming amounts of telemetry can take hours. AI-Powered Root Cause Analysis automatically identifies the root cause of an incident and suggests fixes in seconds, so your team can get back to development (or if they’re on call at 3am, back to sleep.)