Done
Details
Assignee
Santo LetoSanto LetoReporter
Santo LetoSanto LetoPriority
MediumComponents
Labels
Needs QA
YesNeeds Doc
NoPlanned Version/s
Fix versions
Story Points
1Affects versions
Smart Checklist Progress
1/1 - Done
Details
Details
Assignee
Santo Leto
Santo LetoReporter
Santo Leto
Santo LetoPriority
Components
Labels
Needs QA
Yes
Needs Doc
No
Planned Version/s
Fix versions
Story Points
1
Affects versions
Smart Checklist Progress
1/1 - Done
Smart Checklist
Smart Checklist
Smart Checklist
Created March 28, 2024 at 8:12 PM
Updated September 24, 2024 at 9:51 AM
Resolved August 21, 2024 at 9:54 AM
Documenting some feedback about this dashboard.
I believe the root cause here is a “workflow “problem.
In the dashboard “Dashboard MongoDB Collections Overview“ one will first select at the top of the page the cluster, the replica set and the database.
Some charts will be related to the selected database (expected) but some other charts, the ones included under the group “instance level” are more “global”, and include data from other replica set,specifically:
Top 5 Hottest Collections by Read (Total)
Top 5 Hottest Collections by Write (Total)
This is actually documented: https://docs.percona.com/percona-monitoring-and-management/details/dashboards/dashboard-mongodb-experimental_collection_overview.html however, it creates indeed confusion because a database was selected, so the expectations is that the 5 hottest collections by read and write are related to the selected database.
Please note - having such global charts in general is useful. The point here is about mixing the two things (global and database level).
Perhaps we can find a way to better separate / clarify things or have multiple versions (per database and “global”)
Thanks