-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instrument spring-batch: item-level spans #2047
Instrument spring-batch: item-level spans #2047
Conversation
...t/src/main/java/io/opentelemetry/javaagent/instrumentation/spring/batch/item/ItemTracer.java
Outdated
Show resolved
Hide resolved
String stepName = chunkContext.getStepContext().getStepName(); | ||
Span span = | ||
tracer | ||
.spanBuilder("BatchJob " + jobName + "." + stepName + "." + itemOperationName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'd definitely be nice to get some spec issues going for this batch processing stuff
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, definitely - I've filed a spec issue about that (now that my vacation is over I can start working on that 😄 ).
Thanks for calling this out:
It sounds like |
Yes, definitely -- done. |
By the way I ran into an interesting issue with muzzle here: when item level instrumentation was disabled and type instrumentations were not added to the list, by default the |
Another part of spring batch instrumentation, last level of span hierarchy - item-level spans.
This time I couldn't use any listeners for instrumentation, so I'm instrumenting spring batch internal classes. And the item level instrumentation is very chatty, so perhaps it should stay an optional instrumentation even if spring batch ends up being enabled by default.