Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
124 results found
-
Profiler output is confusing
Not so much a feature perhaps as a bug, but it seems that in the profiler page, the chart changes with the time window of interest, e.g. from 24hr to 6 hr or 1hr, but the listing of the namespaces underneath does not. So suppose you think you've fixed an issue and want to check 4 hours later. The chart seems to indicate things are ok, but the namespace table is actually confusing in this case. When you click on an item in a listed namespace (i.e. collection), it goes into the detail view and that one does conform to…
1 vote -
Active link on closed alerts
Currently closed alerts are just a simple text card unlike open alert which does have links. This functionality should be available in closed alert as well.
1 vote -
Time Sensitive Alerts
I would like the ability to (optionally) set a time window for any alert. IE Alert me if average write latency rises above 500 msec from 8am to 8pm. If outside those times don't alert me.
1 vote -
Allow alerts to be created for when a MDB engineer manually intervenes on a cluster issue
This would be for cases when a cluster cannot self heal, and a member of the technical team needs to do a manual intervention. Their activity may show up in the logs after the fact, but there doesn't seem to be a way (currently) to have a proactive notification go out when the update is being made.
Having such an alert would give customers transparency/visibility into what MDB teams are working on, allowing them to focus their attention accordingly (ie. if customers encounter an issue but are alerted that the MDB team is already working on a fix, they'll know…
0 votes
- Don't see your idea?