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

Histogram empty with tokio-console 0.1.1 #262

Closed
benthillerkus opened this issue Jan 19, 2022 · 5 comments · Fixed by #269
Closed

Histogram empty with tokio-console 0.1.1 #262

benthillerkus opened this issue Jan 19, 2022 · 5 comments · Fixed by #269

Comments

@benthillerkus
Copy link

benthillerkus commented Jan 19, 2022

image

Also note that the ID seems to be different, while the rest of the stats is the same.

Last working release

tokio-console 0.1.0

Steps to reproduce

  1. cargo install tokio-console
  2. tokio-console -V -> tokio-console 0.1.1
  3. git clone https://github.com/tokio-rs/console
  4. cd console\console-subscriber\examples
  5. cargo run --example app
  6. tokio-console
    image

System Info

rustc -V -> rustc 1.58.0 (02072b482 2022-01-11)
Windows 10 21H2 build 19044.1466

@benthillerkus
Copy link
Author

The problem was introduced in 095b1ef

benthillerkus referenced this issue Jan 19, 2022
Currently, `console-subscriber` contains a bunch of machinery for
rewriting non-sequential `span::Id`s from `tracing` to sequential IDs
(see #75). Upon thinking about this for a bit, I don't actually
understand why this has to be done on the instrumentation-side. This
seems like extra work that's currently done in the instrumented
application, when it really doesn't have to be.

Instead, the client should be responsible for rewriting `tracing` IDs to
pretty, sequential user-facing IDs. This would have a few advantages:
- it moves some work out of the application, which is always good
- if data is being emitted through an implementation other than
  `console-subscriber`, we will *still* get nicely ordered ids
- this also makes some of the stuff i'm working on in #238 easier

This branch removes ID rewriting from `console-subscriber`, and adds it
to the `console` CLI's `state` module.

Closes #240

Signed-off-by: Eliza Weisman <[email protected]>
@hawkw
Copy link
Member

hawkw commented Jan 19, 2022

Thanks for the report!

I believe this is related to the issue fixed in #251, but it looks like --- for whatever reason --- that commit didn't fix this. I'll have to take a closer look.

@niklaslong
Copy link

I don't think this is platform specific, I've managed to reproduce on M1 and Linux (Ubuntu).

@hawkw
Copy link
Member

hawkw commented Jan 20, 2022

I agree that it's almost certainly not platform specific.

@hawkw hawkw changed the title Histogram empty on Windows with tokio-console 0.1.1 Histogram empty with tokio-console 0.1.1 Jan 20, 2022
jtgeibel added a commit to jtgeibel/console that referenced this issue Jan 28, 2022
Task `Details` are tracked by the remote's `span::Id` while the
`Task::id()` is the friendly id.

The comparison in the view is changed to use the remote span ids and the
field in `Details` is renamed to match.

Fixes: tokio-rs#262
@jtgeibel
Copy link
Contributor

I've opened #269 which should fix this.

hawkw pushed a commit that referenced this issue Jan 28, 2022
Task `Details` are tracked by the remote's `span::Id` while the
`Task::id()` is the friendly id.

The comparison in the view is changed to use the remote span ids and the
field in `Details` is renamed to match.

Fixes: #262
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 a pull request may close this issue.

4 participants