Suggested actions for alerts
Alerts are often very cryptic & don't provide any useful information. For example, when alerting that queries are returning too many rows, without informing me the query or at least the collection, that's very useless. I'm looking at a replication oplog window alert right now and I have no idea what to do about it.
The information in notifications is very less and almost impossible to get an idea about what is going wrong. So, please give us basic solution to this problem.
Basic info like which query returned over 1000 objects or at least clicking the link takes us to that query would be nice at this time.
Hi Timo -
Completely hear you. This has been an often requested feature from our customers. We are working on it and hope to have a solution this year. I will inform this thread as soon as we are close to being done.
Feel free to email me at email@example.com if you wish to discuss further.
Yup, currently receiving hundreds of alerts a day for "Query Targeting: Scanned Objects / Returned has gone above 1000..." but profiler is catching nothing as the queries are still executed fast enough in terms of milliseconds.
I absolutely agree with Eric, just point at the collection/query in question, no need to get fancy with index recommendations or such.
Diego Rodriguez commented
For alerts of type "Query Targeting: Scanned Objects / Returned has gone above 1000...", being able to track the query that triggered the alert or maybe contributed more to it would be of big help.
Please... just add the collection name and query. You can get fancy after that.
AdminAndrew (Admin, MongoDB) commented
Hi Omar, Thanks for flagging this.
We completely agree and want to generally make alerts more prescriptive where possible. There are many classes of alerts so we're starting where we can make the biggest difference. For example for the alert you referenced, we'd like to move to a model in the future where we alert when we can see a way to improve e.g. when we have an index suggestion.