MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
20
VOTE
Not supported for the current status
Status Planned
Categories Atlas Monitoring, Alerts & Observability
Created by Guest
Created on May 21, 2020

RELATED FEEDBACK

Merged feedback
This feedback has been merged into another feedback item To comment or vote on this feedback, please visit CUSTOMER-I-10515 Include Problematic Query Details Directly in Query Targeting Alerts.

add details to alert Query Targeting: Scanned / Returned to identify what triggered it Merged

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.