Alerts
How can I isolate the alerts for one agent into their own log file?
You can track information specific to one agent, microagent or application by writing this information to a log file in an action that is part of a rule. To do this, set up a rule that retrieves specific information (such as free disk space), give it a test that always evaluates to true, and write the important information to a log file. For example, you might create a rule with the data source Performance: LogicalDisk: percent free Space
(Microsoft Windows) or file system: getByPartition: percent free
(Unix) to be collected every five minutes. The rule might have a test such as percent free != -1
which would always be true. The test might have an action such as echo logfile.dat
(which would be prefixed in Microsoft Windows with cmd /c). This would append information on free disk space to a specific log file.
Platform: Not Specified
Version: All
Why did the log parser fail?
If TIBCO Hawk alert or notification messages contain line feed characters, a log file parser cannot properly evaluate the TIBCO Hawk Event Service file, Event.dat
. The line feed characters are usually derived from parameter variable substitution from the following microagents:
• | Logfile:onNewLine
|
• | ${nextLine}
|
• | Custom::executeForString|Number, ${returnString|Number}
|
Avoid using line feed characters in alert or notification messages. If line feed characters cannot be avoided, use the Console API to evaluate alerts and notifications containing line-feeds. You can also use the Hawk 4.1 Event Service microagents in lieu of directly reading Event.dat
.