[COMPASS-461] Rename "hot collections"/"slow operations" to something that includes the command name Created: 28/Nov/16  Updated: 03/Oct/23  Resolved: 07/Aug/22

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Task Priority: Major - P3
Reporter: Anna Herlihy (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Epic Link: COMPASS-2231
Documentation Changes: Not Needed

 Description   

There are a few reasons I think we should rename the tables, or somehow indicate in the UI where the information comes from. We could even say 'mongotop' instead of just 'top'.

  • users should be familiar with some kind of 'top' command, either MongoDB or system top. Would clear up a lot of confusion over what the hot collections table indicates, and why it moves around so much. Especially since there are no other labels.
  • users who are used to mongotop/mongostat can have a reference point.
  • when errors happen, the error message says "top returned error xxx". It can be confusing if it's not clear where that error is coming from or how it changes the charts/tables. I've edited the error messages now so they say "Hot Collections: MongoError: etc." but I think it would be better to be clearer about how it works from the get-go.
  • if a user doesn't understand what top/currentOp/serverStatus is, then they can just ignore it. We can keep the name as "Hot Collections" and add a subtitle, or a label, or something minor so that people who need it can find it.


 Comments   
Comment by Maurizio Casimirri [ 07/Aug/22 ]

I'm going to close this one, is fairly old and we didn't get any other report that would suggest we should improve the current wording

Generated at Wed Feb 07 22:25:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.