Traced annotation

I’d like to host a @Traced annotation in this repository. Being part of the official API would remove this annotation from specific “downstream” repositories, such as:

opentracing-contrib/java-cdi eclipse/microprofile-opentracing

It could also be used here: https://github.com/opentracing-contrib/java-spring-cloud/issues/98

cc @ledor473, @pavolloffay

[ledor473]

So here’s the context and from where that idea came:

When I was looking at instrumenting code via an agent I found this: https://github.com/DataDog/dd-trace-java/blob/master/dd-trace-api/src/main/java/datadog/trace/api/Trace.java

DD provides a small (no dependency) artifact that can be added to pretty much anything without risking to bring a new version of a library and cause a classpath hell.

That would let the user use a common annotation, while picking its own AOP solution. I felt it would be interesting to have that inside OpenTracing, because if we add it inside the Spring library and I’d like to use it with something non-Spring related, it fells wrong.

[wuyupengwoaini]

I am a normal developer and I think @Traced annotation is a very useful function and the same to other developers using opentracing.But adding @Traced annotation to opentracing is not a good choice.Instead,adding @Traced annotation to java-spring-cloud is a good choice.Futhermore, adding new tags to the existing span is also necessary,beacuse it offers a way to bind the trace to the User-defined tags like mobile or orderId and so on.

As for adding a new annotation or adding new method to the @Traced, i am confused.