[Blog Proposal]: Interoperability of Prometheus and OpenTelemetry: Survey results
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 19
Description
Post Title
Interoperability of Prometheus and OpenTelemetry: Survey results
Summary
In this blog post, we will share findings of a survey that OTel End-user SIG (@AndrejKiri, @dhruv-ahuja) ran jointly with Prometheus UX WG (@ArthurSens @vampirarte). The blog post has following outline
Intro
- Key takeaways
- Demographics overview
- Ease of use change over time — 2024 vs 2026 comparison
- Infrastructure metrics instrumentation
- Application metrics instrumentation
- Transformation usage
- Open-ended responses overview
- Interesting observations
Type of Post
Other
Technical Sponsor
@ArthurSens
Author(s)
Dhruv Ahuja (SigNoz),
Andrej Kiripolsky (Grafana Labs),
Ana Muenz (Independent),
Arthur Sens (Grafana Labs)
Additional Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue outline and coordinate with the listed authors and technical sponsor to obtain the survey findings and agree on the 2024 versus 2026 comparison. Draft the Prometheus and OpenTelemetry interoperability post across all listed sections; done means the survey results are accurately covered and the post is ready for publication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus
- Domain
- content, documentation, observability-sre
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100