open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Support for Apache Storm Topology
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Of all the supported libraries that opentelemetry-java-instrumentation currently instruments, there is no support for Apache Storm Topologies. Although it is similar to Kafka in some ways it is quite different and does not have zero code instrumentation.
Describe the solution you'd like
Instrumentation for Bolts and Spouts, which the topology uses and be able to trace the request.
Describe alternatives you've considered
Manual instrumentation of our own code, we have a lot of topologies and instrumenting each topology would just add overhead and not be feasible for large organisations with a lot of constraints on code change. Manual instrumentation may work but it's not zero-code instrumentation, as offered by the Java Agent and the rest of the supported libraries.
Additional context
Please let me know if there is a workaround or if someone has already tried Apache Storm instrumentation.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
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 docs/supported-libraries.md and review how the existing Kafka instrumentation is organized in the Java agent. Investigate Apache Storm’s Bolts and Spouts as the issue describes, then define and implement zero-code tracing for those components. Done means Storm topologies can be traced without modifying topology code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100