Is there a common DevOps language?

Enterprises big and small are realizing the value of adopting DevOps culture and achieving faster innovation, increased customer satisfaction and efficiency improvements. In reality, however, developers and operations often have “lost in translation” problems where developers have one set of tools and languages, and operations teams are utilizing entirely different toolsets and methods. Well, this one organization, found a common language between Dev and Ops, which helped them immensely in their DevOps adoption.


When NBC Universal started on their DevOps journey, they also had different processes and tools they used for development and IT Operations. They wanted to have more visibility into releases performance including understanding how many errors per release, how long is the installation length, and creating the release health benchmarks. Getting ahead of issues and not waiting until their end users report the problems was important to them and they started looking for a solution.

Splunk software gave them that common discussion language. It was a solution that both teams could use and share. Their Splunk platform utilization spread from operations teams into developer teams. With the simple adoption of standardized logging, it was easy to pull granular code release data into Splunk software. At the same time, they got much more details about the performance of their releases in both QA and production. Utilizing Splunk as a common language between teams helped them fine-tune their troubleshooting methodologies, which increased their release frequency.

And as we are seeing that many tech companies are adopting microservices model in the cloud, they have done that as well. And again, Splunk was there to help – it enabled their developers to get engaged much earlier in the process of putting out new microservices.   They were able to understand the performance of their API service down to each back-end server. For each particular request, they knew if it was having the issue or it is going through. As a result, they were able to see much more quickly if the problem with a specific release was related to the particular code build or it if it is a hardware issue. With that insight, the troubleshooting of software releases become streamlined with deep visibility in API services. By getting insight into releases and which builds were more prone to errors, they were able to be much more proactive. They are now able to resolve an issue before it manifests on their website or before it gets even reported.

Because they were able to track the performance of their releases from pre-production, QA and in production, there were able to have many different types of releases pushes on their website daily and freed their developers to focus on innovation.

It is easy to get started with the common DevOps language – just try the Splunk platform!

Stela Udovicic
Sr. Product Marketing Manager
Splunk Inc.

Stela Udovicic

Posted by