Enable SNMP Trap DEBUG logging for outbound notifications
search cancel

Enable SNMP Trap DEBUG logging for outbound notifications

book

Article ID: 388979

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite) VMware Telco Cloud Platform

Issue/Introduction

  • Assist in checking / confirm if the Outbound Setting (SNMP trap) is being successfully generated

Environment

  • Aria Ops, vROps 8.x, 8.14
  • TCP: 5.0.2, 5.1 

Resolution

For the analytics logs to display confirmation that it has sent the SNMP trap, we need to create a logger on ANALYTICS for com.vmware.vcops.platform.notification and set to DEBUG.

  1. Go to Administration > Control Panel > Support Logs:
  2. Ensure that the Group by: dropdown is set to Node.
  3. Select a node from the list and expand the drop-down.
  4. Select ANALYTICS
  5. Click on the gear icon to Edit Properties
  6. Click on the + sign and add the class: com.vmware.vcops.platform.notification 
  7. Search for the com.vmware.vcops.platform.notification class above and set it to DEBUG
  8. The analytics-#######.log file will now detail when an alert is triggered and sent via SNMP:

2025-02-14T13:43:10,156+0000 DEBUG [pool-29-thread-2]  com.vmware.vcops.platform.notification.snmp.SnmpSender.send - Queuing Snmp Trap notification: CANCEL Alert Definition: _CPU Usage gt 0.5, Resource: #### AlertId: ########-#####-####-############, OID: #.#.#.#.#.#.####.#.##.#.#.##; total varbinds: 23
2025-02-14T13:43:10,175+0000 DEBUG [pool-668-thread-1]  com.vmware.vcops.platform.notification.snmp.SnmpSender.send - Sending send SNMP trap... : CANCEL Alert Definition: _CPU Usage gt 0.5, Resource: ####, AlertId:########-#####-####-############, OID: #.#.#.#.#.#.####.#.##.#.#.##; total varbinds: 23
2025-02-14T13:43:10,177+0000 DEBUG [pool-668-thread-1]  com.vmware.vcops.platform.notification.snmp.SnmpSender.send - Successfully sent SNMP trap for alert: CANCEL Alert Definition: _CPU Usage gt 0.5, Resource: ####, AlertId:########-#####-####-############, OID: #.#.#.#.#.#.####.#.##.#.#.##; total varbinds: 23

Note:

  • Remove this logger once the troubleshooting is completed.
  • DEBUG logs collecting on the system add extra load to the cluster and will impact performance if there are too many.