We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since v1.21.0 of the trace Semantic Conventions, new attributes are used:
net.host.name
server.address
net.host.port
server.port
http.target
url.path
url.query
http.scheme
url.scheme
We currently don't map all of these for the OTLP intake, resulting in a poor UI experience. It seems that only the scheme is coming through.
For example, the trace sample UI isn't able to display the URL of the request which started the transaction.
Should be closer to:
The text was updated successfully, but these errors were encountered:
@stevejgordon would you have capacities to take this one on?
Sorry, something went wrong.
@simitt Yes, I'd like to give it a go. Sorry, I thought I'd self-assigned when I opened it! I'm hoping to make some time next week to look at this.
No rush from my side; thanks for taking it on.
stevejgordon
Successfully merging a pull request may close this issue.
Since v1.21.0 of the trace Semantic Conventions, new attributes are used:
net.host.name
->server.address
net.host.port
->server.port
http.target
->url.path
andurl.query
http.scheme
->url.scheme
We currently don't map all of these for the OTLP intake, resulting in a poor UI experience. It seems that only the scheme is coming through.
For example, the trace sample UI isn't able to display the URL of the request which started the transaction.
Should be closer to:
The text was updated successfully, but these errors were encountered: