Skip to main content

The OpenTelemetry Getting Started Survey: Understanding Users' Observability Journeys

Ana Margarita Medina
Senior Staff Developer
ServiceNow

Organizations can face significant challenges, ranging from skill development to user adoption, when implementing new technologies. This is particularly evident in the realm of observability, an increasingly critical area for organizations striving to maintain optimal performance and reliability across digital applications. Recently, the OpenTelemetry End-User SIG surveyed more than 100 OpenTelemetry users to learn more about their observability journeys and what resources deliver the most value when establishing an observability practice.

Most respondents have initiated their observability journey, whether they are in the process of standing up an observability practice or are already well-established. Regardless of experience level, there's a clear need for more support and continued education, especially in helping those who are just starting with observability technologies. When asked what resources they wish they had when getting started with OpenTelemetry, more than half (67%) said they wanted comprehensive documentation, quickly followed by reference implementations for instrumentation (65%), and more detailed tutorials (63%).



When getting started with observability, most respondents are working with containerization technologies, with about 80% using Kubernetes and 63% using Docker.


While quite a few languages are used across organizations, more than 50% of respondents utilize JavaScript, Java, Go, and Python.


The majority of respondents stated that Traces Specification, Instrumentation APIs and SDKs, and Metrics Specification are the most important aspects of their OpenTelemetry journeys.


Observability will continue to be a cornerstone for organizations to not only measure and understand application performance, but to also build resilience into technology stacks. It's imperative for leaders to empower their teams with the necessary tools and knowledge, as they play a pivotal role in the successful adoption and implementation of observability practices. By equipping teams with the proper resources, organizations can overcome the common challenges associated with implementing new technologies, ensuring a smoother transition and maximizing the full potential of their observability initiatives.

Ana Margarita Medina is a Senior Staff Developer at ServiceNow

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

The OpenTelemetry Getting Started Survey: Understanding Users' Observability Journeys

Ana Margarita Medina
Senior Staff Developer
ServiceNow

Organizations can face significant challenges, ranging from skill development to user adoption, when implementing new technologies. This is particularly evident in the realm of observability, an increasingly critical area for organizations striving to maintain optimal performance and reliability across digital applications. Recently, the OpenTelemetry End-User SIG surveyed more than 100 OpenTelemetry users to learn more about their observability journeys and what resources deliver the most value when establishing an observability practice.

Most respondents have initiated their observability journey, whether they are in the process of standing up an observability practice or are already well-established. Regardless of experience level, there's a clear need for more support and continued education, especially in helping those who are just starting with observability technologies. When asked what resources they wish they had when getting started with OpenTelemetry, more than half (67%) said they wanted comprehensive documentation, quickly followed by reference implementations for instrumentation (65%), and more detailed tutorials (63%).



When getting started with observability, most respondents are working with containerization technologies, with about 80% using Kubernetes and 63% using Docker.


While quite a few languages are used across organizations, more than 50% of respondents utilize JavaScript, Java, Go, and Python.


The majority of respondents stated that Traces Specification, Instrumentation APIs and SDKs, and Metrics Specification are the most important aspects of their OpenTelemetry journeys.


Observability will continue to be a cornerstone for organizations to not only measure and understand application performance, but to also build resilience into technology stacks. It's imperative for leaders to empower their teams with the necessary tools and knowledge, as they play a pivotal role in the successful adoption and implementation of observability practices. By equipping teams with the proper resources, organizations can overcome the common challenges associated with implementing new technologies, ensuring a smoother transition and maximizing the full potential of their observability initiatives.

Ana Margarita Medina is a Senior Staff Developer at ServiceNow

The Latest

"AI readiness" has quickly become one of the defining priorities of the modern enterprise. Business decision makers across virtually every industry are working to build roadmaps, solidify strategies, and set expectations around technological investment and adoption. However, at the very same time these leaders are laying their plans, the state of AI continues to change and shift beneath their feet. This raises a fundamental question about the notion of AI readiness: what is it we're actually getting ready for? ...

Genpact and HFS Research recently found that 92% of senior executives at Global 2000 companies believe agentic AI will fundamentally change how work gets done. Yet 85% of them also recognize enterprise debt as a factor limiting their AI value. To move beyond pilots and deliver tangible value, CIOs need to address enterprise debt — the accumulated operational drag from outdated technology, fragmented data, inefficient processes, and talent gaps ...

Proactive is going to become the default expectation, not a nice-to-have. Predicting problems before they happen and fixing them ahead of time will become table stakes, especially for smaller teams and MSPs who cannot afford a big NOC staff ...

The final two installments of the series, Exploring AI Observability, cover predictions from the experts about where AI observability is heading ... In the next few years, tracking your AI won't just be a nice-to-have tool, it will be a survival requirement for businesses ...

Cloud absolutely changed IT for the better. But after more than a decade of using it, companies have also learned something else. Where an application runs matters, and there isn't one environment that makes sense for everything ...

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...