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.
We’ve upgraded our feedback system to better capture, track, and act on your feedback. Here’s what you need to know:
|
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. |
Many alerts are difficult to act on, since they contain information about org & product, then the name of the host that triggered the alert. If you have many clusters in the same project (fairly common) it is very time-consuming / frustrating to go hunt for the relevant cluster. |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
Add the cluster Name in all alerts Output |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
It will remove the Ops frustration and time-consuming process to investigate alerts. |
What steps, if any, are you taking today to manage this problem? |
Using Third party products to allow this. Third party product that can access MongoDB Observalility API. |
as we already include the external customer-facing clustername in the alert details, I will be closing this as "will not implement". However, if there are specific alerts that do not include the cluster name, please do open a new aha so we can address that alert specifically. Thank you!
Hi @Guest can you provide more detail on what alerts are missing the cluster name? Only alerts that are relevant to a host/cluster will have a cluster name field. However, alerts that are relevant to a host should have the clustername in the alert metadata. I've attached two examples down below. If you have specific examples of alerts that are missing that field, please let me know! Thanks, Frank
This is related to https://feedback.mongodb.com/ideas/CUSTOMER-I-9731