-
Notifications
You must be signed in to change notification settings - Fork 717
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
span record method does not record attribute as u16 #3104
Comments
pitoniak32
changed the title
span record does not record attribute as u16
span record method does not record attribute as u16
Oct 12, 2024
(facepalm 😅) I found a work around for the issue. If you I am still wondering if this is expected behavior? tracing::info_span!("request",
{ HTTP_RESPONSE_STATUS_CODE } = None::<u16>,
)
span.record(
HTTP_RESPONSE_STATUS_CODE,
response.status().as_u16() as i64,
); |
If it is, I would like to open a PR adding a little documentation to the Thank you all again for the amazing work that you do! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Version
Platform
Linux d 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Description
I am seeing the incorrect type for an integer attribute / tag values that are exported to an external tracing backend (Jaeger).
I tried this code:
I expected to see the type of the
http.response.status_code
field to be an integer.Instead, it was a string.
if I use an integer directly it will be the correct type:
The text was updated successfully, but these errors were encountered: