add details to alert Query Targeting: Scanned / Returned to identify what triggered it
If you want to catch full scan on collection you could set up alert "Query Targeting: Scanned / Returned > 1".
OPS Manager does not provide any details where it was triggered.
it would be nice to get db/collection/query which caused this issue. Query still can be fast (for example, not many document in collection yet or hardware is idle/fast at the moment) and will not go to slow operation group.
19
votes
Sergey
shared this idea
-
Tyler
commented
Yeah today I get e-mails that say the ratio is off but i cannot tell what query performed the triggering action without spelunking the logs... would be much nicer if it was included in the alert.