Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Allow selecting specific CPUs on OS dahboard #1878

Closed
vladzcloudius opened this issue Feb 4, 2023 · 1 comment · Fixed by #1883
Closed

Allow selecting specific CPUs on OS dahboard #1878

vladzcloudius opened this issue Feb 4, 2023 · 1 comment · Fixed by #1883
Labels
enhancement New feature or request

Comments

@vladzcloudius
Copy link
Contributor

System information

  • Scylla version (you are using): unrelated
  • Are you willing to contribute it (Yes/No): No

Describe the feature and the current behavior/state.
Today the "CPU used" graph on the "OS Metrics" dashboard looks like this:

image

There are two problems:

  1. The by value is probably still shard in the example above. However the node_cpu_xxx metrics use a cpu label.
  2. This dashboard doesn't even have a drop-down to select specific CPU. So even if (1) would be fixed there would be impossible to do something about it. ;)

Who will benefit with this feature?
Everybody.
In particular this would allow looking at IRQ CPUs utilization. Me personally and @avikivity are very interested in this specific use case.

@vladzcloudius vladzcloudius added the enhancement New feature or request label Feb 4, 2023
@amnonh amnonh added this to the Monitoring 4.3 milestone Feb 6, 2023
@amnonh
Copy link
Collaborator

amnonh commented Feb 6, 2023

there's a mixed of unrelated things here, there's no shard/cpu level at the os dashboard, so someone add that manually, if tinstead of adding instance,shard they would have added instance,cpu it would have worked.
So that's not a limitation.
An example:
image

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants