Ericsson Case Study

Ericsson is over 140 years old, with over a 100,000 employees and continues to be one of the leading providers of Communication Technology (ICT) to service providers. In this testimonial, Travis Rowland. the lead devops architect at Ericsson talks about implementing monitoring as part of their DevOps solution.

From Legacy to Cloud

As Ericsson has continued to innovate and adopt new processes in their long 100 year history, their IT infrastructure spanned mainframes, VMware, public cloud (AWS, Azure) and Kubernetes. Various teams in the organizations had adopted different tools based on their needs and there was no unified monitoring solution leading to operational inefficiences.

“We want to use Sensu as the glue to tie all our monitoring together… from Prometheus to AppDynamics, mainframes to Kubernetes”

Travis Rowland, Lead Devops Architect @ Ericsson

The Solution

The Ericsson team funneled all monitoring data from various tools including Prometheus and APM products like AppDynamics into a central Sensu setup. They used Sensu to monitor Kubernetes, AWS, Azure, VMware and also the mainframes - being able to use existing custom Nagios plugins and just drop them into Sensu was a huge advantage for the company.

Once all the data was flowing into Sensu, they used this as a solid foundation to build out a monitoring service for the different teams using the built in Sensu features. The automation features in Sensu allowed not just monitoring, but taking remediation actions automatically in the middle of the night and helped reduce operator fatigue.