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
❯ cargo tree | rg tracing │ │ └── tracing v0.1.40 │ │ ├── tracing-attributes v0.1.27 (proc-macro) │ │ └── tracing-core v0.1.32 │ │ │ └── tracing v0.1.40 (*) │ │ └── tracing v0.1.40 (*) │ │ └── tracing v0.1.40 (*) │ └── tracing v0.1.40 (*) │ │ │ └── tracing v0.1.40 (*) │ │ └── tracing v0.1.40 (*) │ └── tracing v0.1.40 (*) ├── tracing v0.1.40 (*) ├── tracing-log v0.2.0 │ └── tracing-core v0.1.32 (*) ├── tracing-opentelemetry v0.27.0 │ ├── tracing v0.1.40 (*) │ ├── tracing-core v0.1.32 (*) │ ├── tracing-log v0.2.0 (*) │ └── tracing-subscriber v0.3.18 │ ├── tracing v0.1.40 (*) │ ├── tracing-core v0.1.32 (*) │ └── tracing-log v0.2.0 (*) └── tracing-subscriber v0.3.18 (*)
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
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:
tracing::info_span!("request", { HTTP_RESPONSE_STATUS_CODE } = None::<u16>, ) span.record( HTTP_RESPONSE_STATUS_CODE, response.status().as_u16(), // this returns a u16 `pub fn as_u16(&self) -> u16` );
I expected to see the type of the http.response.status_code field to be an integer.
http.response.status_code
Instead, it was a string.
if I use an integer directly it will be the correct type:
tracing::info_span!("request", { HTTP_RESPONSE_STATUS_CODE } = None::<u16>, ) span.record( HTTP_RESPONSE_STATUS_CODE, 400, );
The text was updated successfully, but these errors were encountered:
(facepalm 😅) I found a work around for the issue. If you as i64 the value, it shows as an integer in the trace backends.
as i64
where I stumbled on the fix
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, );
Sorry, something went wrong.
If it is, I would like to open a PR adding a little documentation to the span.record method to give an example of how to record integer types.
span.record
Thank you all again for the amazing work that you do!
No branches or pull requests
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: