What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

When Atlas sends an alert such as "Query Targeting: Scanned Objects / Returned has gone above threshold", the notification does not indicate which specific query is responsible for the high scanned-to-returned ratio.

As a result, we must manually navigate to the Atlas Metrics view, analyze performance charts, correlate timestamps, and then inspect slow query logs or the profiler to identify the problematic query.

This creates additional operational overhead and delays incident response, especially in production environments.

What would you like to see happen?

Describe the desired outcome or enhancement.

We would like Atlas to provide direct visibility into the offending query when a Query Targeting alert is triggered.

Possible enhancements could include:

• Including a summary of the top offending query (or queries) directly in the alert email.

• Providing a direct link in the alert notification that navigates to the exact query in the Performance Advisor or Profiler.

• Highlighting the specific query responsible when accessing the alert inside the Atlas portal.

The key outcome is enabling users to identify the problematic query immediately, without needing to manually correlate metrics.

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

Our team operates production workloads on MongoDB Atlas, and timely detection and resolution of inefficient queries is critical for:

• Maintaining performance and SLA stability

• Preventing unnecessary resource scaling

• Reducing operational response time

• Minimizing cost impact caused by inefficient query patterns

When alerts require multiple manual investigation steps, the time-to-resolution increases. Faster query identification would significantly improve operational efficiency and incident handling.

What steps, if any, are you taking today to manage this problem?

Currently, when we receive this alert, we:

1. Open the Atlas Metrics view from the alert.

2. Analyze the time window when the alert was triggered.

3. Navigate to the Profiler or Performance Advisor.

4. Manually correlate query patterns based on execution time and scanned/returned ratio.

5. Identify and investigate the responsible query.

This manual workflow is repetitive and time-consuming, especially when alerts occur outside business hours.