-
Notifications
You must be signed in to change notification settings - Fork 16
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
[BUG] chart families not showing properly in overview screen #49
Comments
This issue has been mentioned on the Netdata Community. There might be relevant details there: |
Hey @andrewm4894 could you please invite me to the room to take a look? |
just sent invite there - let me know if you don't see it and i can resend. |
@andrewm4894 do you know if this still happens? |
Is this still relevant or we should close it? |
@papazach feel free to close this one. It may have been fairly specific to the anomalies python collector which will be less relevant once we have the anomaly advisor in prod. |
Describe the bug
I have a room with one node. This node about 20 anomalies collector jobs running on it and so has lots of anomalies contexts in the menu on the right.
When i am in the node itself i see correct menus:
But for some reason when i go to the overview for the room i lose those menu's and it has for some reason sort of flattened out all the "System Overview" sections into their own menus for some reason.
To Reproduce
Create a agent with a lot of non standard collectors and/or multiple jobs per collector. Chanage the priority of those jobs to be 80-90 and so appear at top of menu list.
Create a space and room with just that node. Look at the differences between the overview and the node view of the dashboard itself.
Expected behavior
I could see all the menu sections in the overview screen just like i do on the node screen.
Screenshots
As above
Additional context
I'm happy to invite anyone to my room if easier to debug that way as might be a tricky one to recreate.
The text was updated successfully, but these errors were encountered: