The 2019 survey is already wrapped up, and the results are coming soon.
You can get the results as soon as they are published by registering for our blog.
In the meantime, here’s a sneak peek of the study:

  • Tool sprawl is a significant and widespread issue for software engineers. 63% of DevOps Pulse respondents report using more than one observability tool, while close to 14% use five or more.
  • Logging is critical for observability. Over 73% reported using log management and analysis tools to gain observability. Infrastructure monitoring and alerting took second place, both at about 40%.
  • Open source observability stacks are largely preferred over their proprietary counterparts. ELK is the most popular logging tool, Grafana is the most popular metrics tool, and Jaeger is the most popular tracing tool.
  • Tracing has yet to be fully adopted. 66% of DevOps Pulse respondents do not use distributed tracing tools.
  • Serverless is the biggest technical obstacle to observability. Despite more than 40% of respondents adopting serverless, 47% claim serverless technology presents the most challenges for obtaining observability.
  • Machine Learning is gaining momentum as an observability solution. Almost 40% of DevOps Pulse participants use or are considering machine learning solutions to improve observability.
  • As DevOps has become mainstream, R&D teams are sharing the responsibility for observability. DevOps teams are still largely responsible for ensuring observability, but Developers and Operations are not far behind.