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
Created by Guest
Created on Feb 24, 2020

RELATED FEEDBACK

SNMP traps for `AUTOMATION_AGENT_DOWN`, `MONITORING_AGENT_DOWN`, `BACKUP_AGENT_DOWN` alert types does not contain hostname information

*What is the problem that needs to be solved?* SNMP traps for `AUTOMATION_AGENT_DOWN`, `MONITORING_AGENT_DOWN`, `BACKUP_AGENT_DOWN` alert types does not contain hostname information in `.1.3.6.1.4.1.41138.1.1.1.4` (`.iso.org.dod.internet.private.enterprises.mms.server.serverMIBObjects.mmsAlertObject.mmsAlertHostAndPort`) OID. *Why is it a problem? (the pain)* User is blocked to act quickly on the alert and identify the host where Ops Manager's Automation/Monitoring/Backup Agent is in `DOWN` state. Missing `:` information at `.1.3.6.1.4.1.41138.1.1.1.4` SNMP OID does not allow user to map `AUTOMATION_AGENT_DOWN`, `MONITORING_AGENT_DOWN`, `BACKUP_AGENT_DOWN` alert types into a particular hostname.
  • Attach files
  • Guest
    Apr 3, 2020
    Hi, In order to map fields with the BMC ticketing. Its essential to have these text fields org name and Project name. Else , it needs lot of time and effort from netcool side. While we get other output , adding these fields will be good to have it mapped for the incident details.
    Reply