-
Notifications
You must be signed in to change notification settings - Fork 528
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
OTel array attributes not recorded as labels #5663
Comments
I did it for transactions, but forgot to do it for spans too. Also resource attributes. |
Testing against #5704, array attributes at the resource level are correctly handled, but when I add them at the span level they still aren't appearing. Single value attributes added at the span level aren't appearing for me now, either. version: gist: https://gist.github.com/stuartnelson3/61b9e61bf4ab78955dc0a7844d26c626 (updated to add resource attributes) |
@stuartnelson3 I just ran the latest 7.14-SNAPSHOT image, and pointed your gist at it:
There's 3 events here: transaction, span, and latency histogram metric. The transaction only has the resource attributes, while the span has both resource and span attributes. That's expected from the code, because only the span (getUser) has span attributes specified. Were you looking at the transaction doc and not span doc maybe? |
correct, I was looking at the transactions index. thanks! |
APM Server version (
apm-server version
):Description of the problem including expected versus actual behavior:
When sending traces using an attribute array, the values do not appear in the document in elasticsearch. When changing the code to send a single attribute value, the value appears as a label.
single attribute:
Steps to reproduce:
EXPORTER_ENDPOINT=localhost:8200 go run main.go
curl http://localhost:8080/users/123
GET apm-7.14.0-span-000001/_search
The gist linked above has a commented out line at the bottom setting a single string attribute.
The text was updated successfully, but these errors were encountered: