Skip to content
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

CXF-9055 Follow OpenTelemetry semconv for trace span and its attributes #2062

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

csemaan1A
Copy link
Contributor

@csemaan1A csemaan1A commented Sep 11, 2024

  • Add missing span attributes to comply with OpenTelemetry semantic conventions
  • Test the span attribute names and values
  • Couldn't add the attributes "network.protocol.version" for the client http span, because we didn't find a way to find its value.

Link to the Jira ticket: CXF-9055 Follow OpenTelemetry semantic conventions for trace span and its attributes

@reta
Copy link
Member

reta commented Sep 11, 2024

Thanks for the pull request, @csemaan1A ! I would suggest to preserve the span name (as you highlighted, it is breaking) to have consistent behavior across CXF tracing integrations, thank you.

@csemaan1A
Copy link
Contributor Author

Thanks for the pull request, @csemaan1A ! I would suggest to preserve the span name (as you highlighted, it is breaking) to have consistent behavior across CXF tracing integrations, thank you.

I renamed it to have only the path to be aligned with the semantic convention of OpenTelemetry.

Keep in mind, that the server span name is set to path, not the full URL.
So what do you think?

@csemaan1A csemaan1A force-pushed the add-semantic-convention-attributes branch from 0536ce2 to 31a3bb2 Compare September 12, 2024 09:07
@reta
Copy link
Member

reta commented Sep 12, 2024

I renamed it to have only the path to be aligned with the semantic convention of OpenTelemetry.

Thanks, I read the recommendations and I don't see much of controversy here. Yes, the span name has more than path (too specific?) but what is more important - we are not adding blank implementation. I would prefer to not break things.

@csemaan1A csemaan1A force-pushed the add-semantic-convention-attributes branch from 31a3bb2 to 21a1fcc Compare September 12, 2024 12:39
@csemaan1A csemaan1A force-pushed the add-semantic-convention-attributes branch 2 times, most recently from 23da77b to 1430234 Compare September 12, 2024 14:23
* Add missing span attributes to comply with [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-spans/)
* Test the span attribute names and values
* Couldn't add the attributes "network.protocol.version" for the client http span, because we didn't find a way to find its value.

Link to the Jira ticket: [CXF-9055 Follow OpenTelemetry semantic conventions for trace span and its attributes
](https://issues.apache.org/jira/browse/CXF-9055)
@csemaan1A csemaan1A force-pushed the add-semantic-convention-attributes branch from 1430234 to 248e120 Compare September 13, 2024 08:39
@reta reta merged commit 1f0355e into apache:main Sep 13, 2024
4 checks passed
@reta
Copy link
Member

reta commented Sep 13, 2024

Thanks a lot @csemaan1A !

reta pushed a commit that referenced this pull request Sep 13, 2024
…es (#2062)

* Add missing span attributes to comply with [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-spans/)
* Test the span attribute names and values
* Couldn't add the attributes "network.protocol.version" for the client http span, because we didn't find a way to find its value.

Link to the Jira ticket: [CXF-9055 Follow OpenTelemetry semantic conventions for trace span and its attributes
](https://issues.apache.org/jira/browse/CXF-9055)

(cherry picked from commit 1f0355e)
reta pushed a commit that referenced this pull request Sep 14, 2024
…es (#2062)

* Add missing span attributes to comply with [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-spans/)
* Test the span attribute names and values
* Couldn't add the attributes "network.protocol.version" for the client http span, because we didn't find a way to find its value.

Link to the Jira ticket: [CXF-9055 Follow OpenTelemetry semantic conventions for trace span and its attributes
](https://issues.apache.org/jira/browse/CXF-9055)

(cherry picked from commit 1f0355e)
(cherry picked from commit 9be1640)

# Conflicts:
#	integration/tracing/tracing-opentelemetry/src/main/java/org/apache/cxf/tracing/opentelemetry/jaxrs/OpenTelemetryProvider.java
reta pushed a commit that referenced this pull request Sep 14, 2024
…es (#2062)

* Add missing span attributes to comply with [OpenTelemetry semantic conventions](https://opentelemetry.io/docs/specs/semconv/http/http-spans/)
* Test the span attribute names and values
* Couldn't add the attributes "network.protocol.version" for the client http span, because we didn't find a way to find its value.

Link to the Jira ticket: [CXF-9055 Follow OpenTelemetry semantic conventions for trace span and its attributes
](https://issues.apache.org/jira/browse/CXF-9055)

(cherry picked from commit 1f0355e)
(cherry picked from commit 9be1640)

# Conflicts:
#	integration/tracing/tracing-opentelemetry/src/main/java/org/apache/cxf/tracing/opentelemetry/jaxrs/OpenTelemetryProvider.java
(cherry picked from commit 7a15456)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants