The most recent content from our members.
At the moment received SNMP- and Syslog Traps are only parsed and written directly into NPM database The alerting interface for Traps has nothing to do with the NPM advanced alerting engine - nothing else happens in NPM with that valuable collected information. Additionally a received critical Trap has no correlation to…
I came across this:modifying custom properties using swisinvoke.exe? I think this would be good implemented as an internal action in the snmptrap and syslog servers so an external program does not need to be invoked. this would make linkage between the syslog and trap servers and the advanced alert engine easier. the…
when defining a SNMP Trap Action in LEM I can decide between "HostIncident"; 2HybridIncident" and "NetworkIncident"; all incidents have different predifiened fields to put information in. the trap itself comes with the following varbinds: .1.3.6.1.4.1.11307.12.x But I cannot find a documentation about the definition about…
has anybody yet successfully created a rule with a SNMPTrap Action that fires when a correlation is configured based on the following (e.g.): Correlation Time 2 Alerts within 40 seconds when I reduce the number of alerts to 1, the rule fires, if the number is raised, it fires no more... The basic alert is a…
for the SNMP Trap Action I would like to see a new field where free text could be added along with any (or all) of the variables of the Alert Details; this field should be available for all of the 3 incident types (Host-, Hybrid-,Network-Incident) and it should have the same OID for all three incidents; having 5 of these…
It looks like you're new here. Sign in or register to get started.