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.

We want to ensure that index build failures in MongoDB Atlas are not missed. Currently, if an index build fails, Atlas does not raise any alert, which means teams may continue operating with missing or partially built indexes without knowing. This leads to degraded performance, unexpected query slowdowns, and difficult debugging. Alerting on index build failures would give early visibility and prevent silent performance regressions.

What would you like to see happen?

Describe the desired outcome or enhancement.

MongoDB Atlas should automatically trigger alerts whenever an index build fails. This alert should appear in the Alerts section and support all existing notification channels (email, Slack, PagerDuty, webhook, etc.). This would ensure index failures are immediately visible and actionable, similar to other operational issues.

Why is this important to you or your team?

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

Index build failures directly impact query performance and system reliability. Without alerts, these failures go unnoticed and can cause silent performance degradation, increased latency, and unexpected production issues. Our team relies on accurate indexing for predictable query behaviour, and early visibility into index build failures helps us prevent incidents, reduce debugging time, and maintain SLAs.

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

Today, we have to manually monitor index creation. These approaches are reactive, time-consuming, and can still miss failures. There is no automated or reliable way within Atlas to detect and surface index build issues proactively.