OpenTelemetry Adoption & Readiness Assessment

Welcome to the OpenTelemetry Adoption & Readiness Survey. This survey takes approximately 6–8 minutes and covers your experience with observability tooling and OpenTelemetry. Your responses are completely anonymous and will be reported only in aggregate to inform tooling and adoption strategy. There are no right or wrong answers — we are interested in your honest experience. Participation is voluntary, and you may stop at any time.

Which best describes your primary role?

• Backend developer
• Frontend developer
• Full-stack developer
• Site Reliability Engineer / DevOps
• Data/ML engineer
• QA/Testing engineer
• Software architect / Tech lead
• Platform engineer
• Other (please specify)

Which observability tools have you used in the last 6 months? (Select all that apply.)

• Prometheus
• Grafana
• Jaeger
• OpenTelemetry SDK
• OpenTelemetry Collector
• Elastic APM
• Datadog
• New Relic
• Splunk Observability
• AWS X-Ray
• Azure Monitor
• Google Cloud Operations Suite
• None of the above
• Other (please specify)

Which best describes your organization's current OpenTelemetry adoption stage?

• Not considering
• Evaluating
• Piloting in one or a few services
• In limited production
• Broad production across services

What are the biggest blockers to adopting or expanding OpenTelemetry in your organization? (Select up to 5.)

• Limited time or competing priorities
• Unclear ROI / benefits
• Learning curve or lack of expertise
• Language or framework gaps
• Lack of organizational buy-in
• Tooling or integration maturity
• Data volume or storage cost concerns
• Performance overhead concerns
• Security/PII/governance concerns
• We're satisfied with current vendor tooling
• No need identified yet
• Other (please specify)

Which areas are your next targets for OpenTelemetry instrumentation in the next 6 months? (Select all that apply.)

• Java services
• Node.js services
• Python services
• Go services
• .NET services
• Mobile apps (iOS/Android)
• Browser RUM
• Databases
• Message brokers/streaming (e.g., Kafka)
• Serverless functions
• Batch/ETL workloads
• Other (please specify)

We'd like to understand more about your experience with observability and OpenTelemetry. An AI moderator will ask a few brief follow-up questions based on your earlier responses.

How many years of professional software development experience do you have?

• 0–1
• 2–4
• 5–9
• 10–14
• 15+
• Prefer not to say

Thank you for completing this survey! Your responses are anonymous and will be used in aggregate to identify adoption patterns and prioritize improvements to the OpenTelemetry ecosystem.

What is your primary programming language for services you work on today?

• Java
• JavaScript/TypeScript
• Python
• Go
• C#/.NET
• C/C++
• Ruby
• PHP
• Rust
• Other (please specify)
• Prefer not to say

How familiar are you with OpenTelemetry concepts and components?

Approximately what percentage of your production services are currently instrumented with OpenTelemetry?

• 0%
• 1–10%
• 11–25%
• 26–50%
• 51–75%
• 76–99%
• 100%
• Not sure

Which of the following support resources would be most helpful for your OpenTelemetry adoption? (Select up to 3.)

• Official documentation improvements
• Language-specific getting-started guides
• Reference architectures and deployment patterns
• Hands-on workshops or training sessions
• Internal champions / OTel working group
• Vendor-neutral migration tooling
• Community forums or Slack channels
• Consulting or professional services
• Other (please specify)

How likely is your team or organization to adopt or expand OpenTelemetry usage in the next 6 months?

Based on your responses in this survey, if you could change one thing about OpenTelemetry or its ecosystem, what would it be?

Where are you primarily based?

• North America
• Europe
• Asia-Pacific
• Latin America
• Middle East
• Africa
• Other (please specify)
• Prefer not to say

Where do your production workloads run today? (Select all that apply.)

• Kubernetes
• Serverless (e.g., AWS Lambda, Azure Functions)
• Containers without an orchestrator
• Virtual machines (VMs)
• Bare metal
• PaaS (e.g., Heroku, App Engine)
• On-premises data center
• Hybrid or multi-cloud

Which OpenTelemetry components or capabilities are you using today, if any? (Select all that apply.)

• OTel SDKs (language libraries)
• OTel Collector (any deployment)
• OTLP export protocol
• Auto-instrumentation
• Manual instrumentation
• Semantic conventions
• Sampling configuration (e.g., tail-based)
• Not using OTel yet

Rank the following outcomes by how important they are to your organization's OpenTelemetry goals (most important first).

1. Faster incident detection and response
2. Better root-cause analysis
3. Cross-service traceability
4. Standardized telemetry across teams
5. Vendor portability / avoiding lock-in
6. Cost control and optimization
7. Improved application performance
8. Security/compliance visibility

Approximately how many employees are in your organization?

• 1–10
• 11–50
• 51–200
• 201–1,000
• 1,001–5,000
• 5,001–10,000
• 10,001+
• Prefer not to say