-
Type:
Task
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
None
-
None
-
None
-
None
-
None
-
None
-
None
There have been impactful escalations from a business perspective (such as HELP-81069), where the on-premises deployment encountered an issue that had already been analyzed and resolved in one of the subsequent releases. These occurrences have a tangible impact on the customer's business and could have been avoided if the customer had updated their infrastructure — likely had they been aware of the existence of this critical issue.
These problems are already described in the release notes of the released versions; however, the recurrence of such escalations indicates that this information is either not being read or not given sufficient consideration.
The goal of this ticket is to assess the possibility that our automation tools provided to customers for on-premises deployments (Ops Manager) could integrate with a remote MongoDB service to fetch the list of known critical bugs. This would enable automatic notifications to customers (or auto-patch) regarding the urgency of server updates if their environments are affected. Feasibility analysis would be needed to assess implementation viability.
The ultimate objective is to eliminate — or at least minimize — escalations like HELP-81069.
More information on the origin of this request is available in Postmortem: HELP-81069 Epic Games issue of Sep 3, 2025. On the other hand, SERVER-115828 aims to evaluate a manual approach.