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)
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 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)
How familiar are you with OpenTelemetry concepts and components?
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
What are the biggest blockers to adopting or expanding OTel in your organization? (Select all that apply.)
- 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 best describes your organization’s current OpenTelemetry adoption?
- Not considering
- Evaluating
- Piloting in one or a few services
- In limited production
- Broad production across services
Approximately what percentage of your services are instrumented with OTel today?
Allocate 100 points to the outcomes you most want from OTel.
Rank the biggest challenges for an org‑wide OTel rollout (top = biggest).
How helpful would each of the following be for your OTel adoption?
Which areas are your next targets for OTel 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)
How likely are you to adopt or expand OTel in the next 6 months?
Attention check: To confirm you’re paying attention, please select “Agree.”
- Agree
- Disagree
- Prefer not to answer
How many years of professional software development experience do you have?
- 0–1
- 2–4
- 5–9
- 10–14
- 15+
- Prefer not to say
Where are you primarily based?
- North America
- Europe
- Asia‑Pacific
- Latin America
- Middle East
- Africa
- Other (please specify)
- Prefer not to say
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
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
If you could change one thing about OTel or its ecosystem, what would it be?
Max 600 chars
Welcome! This brief survey takes about 6–8 minutes. Please answer based on your current work. Your responses are anonymous.
AI Interview: 2 Follow-up Questions on OpenTelemetry
Thank you for participating! Your feedback will help improve OpenTelemetry and its ecosystem.