Sidebar
products:cockpit.old:6.6:monitorsguide:netweaver:applicationlogs
Book Creator
Add this page to your book
Add this page to your book Book Creator
Remove this page from your book
Remove this page from your book 
Manage book (
Help Table of Contents
Application logs
Purpose
This monitor will focus on the application logs of the system. You can monitor log entry status, as well as the messages contained in a log. To enable the surveillance, you will have to define a list of objects and sub-objects that you want to watch.
Note:It is not possible to set filters on text messages contained in the logs, only importance and severity can be monitored.
Configuration hints
Use the “Add Line” button to discover existing log objects and sub-objects in the system. Then select the type of check: - LOG: Compares the threshold to the number of logs matching the filter - MESSAGES: Compares the threshold to the total number of messages contained in the logs matching the filters. Then you can set specific filters on the client, the user, the transaction and the mode. Select the minimum severity class of the log that you want to take into account.
If check type is MESSAGES and aggregate is set to false, then the threshold will be compared to the number of messages of each single log entry and report an alarm for each one above the threshold.
Surveillance table
| Parameter | Description |
|---|---|
| Active | To enable or disable a rule |
| Check type | Defines how the threshold will be used. LOG: Compare the threshold to the number of log entries matching the filter. MESSAGES: Compare the total number of messages contained in log entries to the threshold. |
| Object | The log object to check for. Use “Add Line” to discover all available objects |
| Sub-object | The log sub-object to check for. Use “Add Line” to discover all available objects |
| Client | To filter results for specific client. You can use regular expressions |
| User | To filter results for specific user. You can use regular expressions |
| Transaction | To filter results for specific transaction. You can use regular expressions |
| Report | To filter results for specific report. You can use regular expressions |
| Mode | To filter results for specific mode. You can use regular expressions |
| Minimum log class | The minimum importance level for a log entry to be taken into account. You can select for example only logs containing very important messages |
| Type | The type of log messages to look for. You can for example look for ABORTED messages only |
| Threshold | The number to which will be compared the number of logs or the number of messages (depends on check type) |
| Aggr. | If set to true, only one alarm per line will be sent, reporting the number of log entries matching the filter. If set to false, one alarm per log entry will be sent. |
| Severity | The severity of the alarm generated if threshold is breached. |
| Alarm tag | A field to use if you want to prefix alarm message with a given text. |
| Alarm | Enable/disable alarm sending |
| Metric | Enable/disable metric sending |
| Report | For future usage in reports |
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/cockpit.old/6.6/monitorsguide/netweaver/applicationlogs.txt · Last modified: 2024/05/01 18:39 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
