Hi,
I'm able to create Custom SQL alerts on Solarwinds based on Trap Type, thanks to the previous posts in the this forum and especially detailed responses from RichardLetts on various questions in particular!
But looks like the requirements that we have is bit more complex. The 'Trap Type' is going to be the same in our case for different nodes and the only way we can uniquely identify a SNMP trap is based on the SNMP 'Trap Details' as highlighted below (It could be swift.storage1, swift.storage2 etc and we will be scaling to hundreds of them)
TIME OF TRAP | IP ADDRESS | HOSTNAME | COMMUNITY | TRAP TYPE | TRAP DETAILS |
3/15/2016 9:05:34 PM | 10.x.x.2xx | 10.x.x.2xx | public | SNMPv2-SMI:enterprises.39154.3.1.0.26 | enterprises.39154.3.1.1.1 = Low available disk space on Swift.storage.1 enterprises.39154.3.1.1.6 = 4 enterprises.39154.3.1.1.5 = swift.storage.1 enterprises.39154.3.1.1.2 = 95 enterprises.39154.3.1.1.3 = 3 enterprises.39154.3.1.1.4 = 409 snmpTrapOID = SNMPv2-SMI:enterprises.39154.3.1.0.26 sysUpTime = 7 days 22 hours 14 minutes 58.03 seconds |
- I'm able to get specific values from the Trap Details while configuring the action of a alert, but not able to figure out how do I create Alert itself based on partial content of trap detail itself (for e.g -swift.storage.1) ?
- If it's possible to do what is mentioned above, how do I write a reset condition for the same ?
- We also get an SNMP Traps once the node issue is resolved (some times automatically because of self healing). For example, the above SNMP trap , under trap details, you can see the message as Low available disk space on Swift.storage.1 and in the trap below it says it's resolved. Please note that Trap Type will be different for these info traps. How do we reset the alert created in the first trap based on the second trap shown below ?
TIME OF TRAP | IP ADDRESS | HOSTNAME | COMMUNITY | TRAP TYPE | TRAP DETAILS |
3/15/2016 9:10:45 PM | 10.x.x.2xx | 10.x.x.2xx | public | SNMPv2-SMI:enterprises.39154.3.1.0.27 | enterprises.39154.3.1.1.1 = Available disk space on Swift.storage.1 is sufficient enterprises.39154.3.1.1.6 = 4 enterprises.39154.3.1.1.5 = swift.storage.1 enterprises.39154.3.1.1.2 = 95 enterprises.39154.3.1.1.3 = 3 enterprises.39154.3.1.1.4 = 409 snmpTrapOID = SNMPv2-SMI:enterprises.39154.3.1.0.26 sysUpTime = 7 days 22 hours 14 minutes 58.03 seconds |
Any inputs or guidelines will be of great help !
Thanks & Regards,
Antony.