Using
names such as MyTrigger probably won??™t work well. It??™s important to create a descriptive name
that you??™ll recognize easily. Make sure you make the name unique by adding some elements for
the event log entry that it monitors. For example, WinMgmtWarning63 would be a good name
for an event generated by the Windows management service at the warning level for event identifier
number 63.
/L
log
Specifies the Windows event log to monitor. The three common logs include Application,
System, and Security. The DNS Server and Directory logs commonly appear on servers. You
can also specify any custom log. You can use wildcard characters to define the log name. The
default value is ???*??? (without the quotes), which is all of the event logs on the specified machine.
/EID
id
Specifies which Event ID to monitor in the event log. This value is application specific,
so you need to know which Event ID an application will use for a particular requirement.
/T
type
Specifies the Event Type to monitor in the event log. The valid values include
ERROR
,
INFORMATION
,
WARNING
,
SUCCESSAUDIT
, and
FAILUREAUDIT
. The
SUCCESSAUDIT
and
FAILUREAUDIT
only appear in security logs.
Pages:
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063