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 receiving MongoDB Atlas alert webhooks, the payload only includes the alert ID and does not include a human-readable identifier such as the alert name. This makes it difficult to quickly understand and act on alerts without additional lookups. The core problem is the lack of sufficient context in the webhook payload to identify the alert in a meaningful way.

What would you like to see happen?

Describe the desired outcome or enhancement.

We would like the webhook payload for Atlas alerts to include the alert name (or another human-readable identifier) alongside the alert ID so that each alert can be immediately identified without requiring additional lookups.

Why is this important to you or your team?

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

Including the alert name would simplify our alert processing workflows, reduce operational complexity, and improve reliability. It would eliminate the need for maintaining and synchronizing a separate mapping of alert IDs to alert names, making alerts easier to interpret and act on in real time.

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

Currently, we maintain a custom mapping of alert IDs to alert names outside of Atlas and reference that mapping when processing webhook events. This requires ongoing maintenance as alerts are created or updated and introduces additional complexity and potential points of failure in our system.