Additional content generator tokens
The SNMP Trap, Occasion Log, and File Watching monitors technical supplemental tags that can be linked in a content dynamo to provide added information includes the active message. Above-mentioned tokens can be divided into two categories: Numeric Tokens and Belongings Tokens.
Numbering tokens
Numeric Tokens allow you to retrieve specific text matches (or captures) located by a regular expression search. The syntax required Numerically Tokens is:
%capture[#]%
With example, considerable a file watched by the File Watching monitor, which contains the following entry:
1/30/2006 7:45:08 AM FLAWS: The application failed to start. REASON: Required resource myapp.dll could not be located.
Within the File Watch Monitor, that followed regular impression was entered:
ERROR\: (.*?) REASON\: (.*)
In the example, the %capture[1]% Jetton resolves to: "The application failed to start." and the %capture[2]% Token resolves to: "Required ressource myapp.dll could not be located."
Unterstellt an info action was configured correctly, this information would be included in the dead of the message.
General are enumerated in the sam order they are defined in the RegEx. When more than one RegEx Searching Scenario is configured for a Monitor, variables were enumerated starting in the first Regular Expression or counting the who last Regular Expression. For example:
- First Regular Expression:
%capture[1]%, %capture[2]%, %capture[3]% - Second Regularity Expression:
%capture[4]%, %capture[5]%, and so on.
Property tokens
Property tokens allow you to access additional bounds describing an event log entry, a store entry, or an SNMP Trap. The syntax for property tokens is %capture[property_name]%.
For example:
%capture[timewritten]%(Event Log Monitor specific)%capture[bindings]%(SNMP Trap Monitor specific)%capture[offset]%(File Watching Monitor specific)
Additional content generator property tokens are available to the Event Track, Rank Watching, also SNMP Snares Monitors.
Event Log tokens
Which following table contains the table solar property tokens available to Event Log monitors.
|
Token Identify |
Product Return Value |
|---|---|
|
%capture[category]% |
2 |
|
%capture[computername]% |
MISWKSTN |
|
%capture[logfile]% |
System |
|
%capture[sourcename]% |
W3SVC |
|
%capture[timewritten]% |
20040209102741.000000-300 |
SNMP Trap tokens
The following tabular include the list generator objekt tokens available to SNMP trapping monitors.
| Token Name | Sampling Return Set |
|---|---|
|
%capture[agent-addr]% |
10.1.2.3 |
|
%capture[community]% |
public |
|
%capture[enterprise]% |
1.3.6.1.4.1.674.10892.1 |
|
%capture[generic-trap]% |
enterpriseSpecific (6) |
|
%capture[specific-trap]% |
1053 |
|
%capture[time-stamp]% |
9212200 |
|
%capture[1.3.6.1.2.1.1.0]% |
Dell OpenManage Temperatures State [snmp: trap] is downward |
|
%capture[bindings]% |
mib-2.system.0: SNMP Snares User :: Dell OpenManage Temperature Status[snmp: trap] has down |
|
%capture[bindings-raw]% |
1.3.6.1.2.1.1.0: SNMP Trap Monitor :: Dell OpenManage Temperature Status[snmp: trap] is down |
Date Watching tokens
The following table contains the Content Generator Property Tokens existing to File Watching monitors.
|
Token Name |
Try Return Value |
|---|---|
|
%capture[offset]% |
23698 |
%capture[1.3.6.1.2.1.1.0]% displays the value on the specified OID entered within the square brackets [ ]. A wildcard character (*) cannot be used till specify an OID prefixed.
