MongoByte MongoDB Logo

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.

Add new feedback Subscribe
Status Submitted
Categories Enterprise Advanced
Created by Guest
Created on Apr 6, 2020

RELATED FEEDBACK

Add hostname/port attributes into all Cluster/Replica Set alert types

**_What is the problem that needs to be solved?_** Add hostname/port attributes into all Cluster/Replica Set alert types generated via SNMP Alert Traps, Ops Manager's Public API calls (Project/Global Alerts) and Alert Webhooks (Project/Global Alerts). **_Why is it a problem? (the pain)_** Hostname/port attributes are currently missed in Cluster/Replica Set alert types and we only provide a name of the Cluster/Replica Set for which the alert was generated. Operator who watch Monitoring System (the one that receive Ops Manager Alerts) needs to see hostname/port information of a Shard/Replica Set for which such alert was generated, in order to quickly understand to where that Ops Manager's Alert is related to. Monitoring System (the one that receive the alert from Ops Manager) needs to do additional work for alert received (via additional API calls (if possible at all)) in order to get hostname/port for each process of Cluster/Replica Set.
  • Guest
    Jun 26, 2020
    @Brian, we already have `mmsAlertHostAndPort` field (.1.3.6.1.4.1.41138.1.1.1.4 OID) in SNMP Alert Traps model, so hostname/port attributes should be set there if this Feature Request will be implemented.
    Reply
  • Guest
    Jun 26, 2020
    The `mmsAlertSummary` field of the alert traps would be a reasonable place to list the replica set member hostnames and port numbers for SNMP delivery.
    Reply