In this menu you can find or create a list for passing traps to monitoring process. Trap Filters are used for determining if traps received by SONARPLEX will be passed to monitoring process or blocked otherwise.
Notice: Filters are defined by human readable name, source address, Object Identifier (OID) and resulting service state.
To edit or create a new or existing trap filter, proceed as follows:
- Open the
> Configuration > Host Checks and select a command name for host checks (see picture below).Insert excerpt _AdminWeb _AdminWeb nopanel true Enter your settings or change it, as described in the table below.
Parameter
Description
Filter name
Filter name to be used as filter ID - must be unique. Allowed characters are a-z, A-Z, 0-9 and underscore (_).
Source address
Address of host sending the trap (empty address means that any source address is allowed to pass appropriate trap).
OID
Object Identifier (OID) of the trap. If specified OID matches OID of appropriate trap or any of its bound data OIDs, the trap will be passed to the monitoring process.
Resulting service state
Service state created by determining passive check result for service matching trap parameters.
Following values are allowed: “OK”, “WARNING”, “CRITICAL”, “UNKOWN”
Notice: There are two different options to determine service state: The filter option above and service definition. By default the filter option is used. This which may be changed by service definition afterwards during trap processing.
You can also see the list of traps, which are recently received. List can be toggled between by process level trap properties unfiltered, filtered, processed and all traps.
Property | Description |
---|---|
unfiltered | No appropriate filter found, trap has not been passed to monitor process. |
filtered | Filter found, trap has been passed to monitor process. |
processed | Filter found, trap has been passed to monitor process and used for service check result determination. |
all | All traps recently received. |
A detailed view of appropriate unfiltered trap can be used to define new filters based on trap items Source Address and OID by using the button add to filters.
Notice: If no filters are defined, all traps are passed to monitoring process. Trap history size is limited by SNMP Configuration Option Max number of trap history entries.