Windows applications and services log
When this service has a scan interval of less than 5 minutes, the agent may take longer than the scan interval to gather the metrics. As a result, you may notice some scan intervals are not populated.
The Windows Applications and Services Log enables you to monitor the Applications and Services Logs on Windows devices, similar to the Windows Event Log Service.
Since you can assign up to 1,000 instances of this service to a device, you can give each instance a Service Identifier. The Service Identifier is included in email notifications and on service-related displays, including the Active Issues view and the Status tab when editing a device. This enables you to maintain multiple instances of the Windows Applications and Services Log in an organized fashion.
For some sources, the agent may not be able to retrieve an event description due to:
- the relevant Windows registry keys do not exist,
- the relevant Windows registry keys do not contain valid data, or
- the Event Message files are corrupted or were not found.
For any of these scenarios, the following message appears: "The description for Event ID (Event ID Number) in Source (Source Name) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer."
Log Monitoring Options
To help in processing Windows logs, you can configure how the Windows agent reads the data from the log. Click Administration > Defaults > Agent and Probe settings and click the Agent tab. Configure the following options:
- Multiline entries - evaluate each line separately
- Perform Case Insensitive Text Searches
Some events in the Windows Event log include a line break, \n, in their description or source. When this option is enabled the Windows agent evaluates each line separately. If this option is disabled, all lines are treated as a single text string.
If this option is enabled, the regex provided in the Event Source field is treated as case insensitive. If this option is disabled, the regex provided in the event source is treated as case sensitive.
| Service Type | WMI |
| Instances on a Device | 1000 |
| Device Class | Laptop - Windows, Server - Windows, and Workstation - Windows |
| Monitored By | Windows agent, Windows probe |
| Generate a Notification when an Event is detected | After adding a notification trigger/profile, selecting this checkbox directs the service to generate notifications whenever it detects events. |
| Scan Interval | 30 minutes |
| Minimum Scan Interval | 1 minute |
| Include List | The event IDs that you would like to monitor. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters. Spaces are not allowed. |
| Exclude List | The event IDs that you would like to exclude from monitoring. You can specify individual event IDs or a range of comma-separated event IDs. For example: 100,200,250-400,500-650 This field allows a maximum of 200 characters. |
| Event Source Include Filter | The names of the sources that you would like to monitor. Values must be in CSV format. For a range of Event IDs, use a dash. Use wildcard string expressions separated by commas to match event sources, included in the list of reported events. For Example, using This field does not support regular expressions. |
| Event Source Exclude Filter | The names of the Event Log sources that you would like to exclude from monitoring. Values must be in CSV format. For a range of Event IDs, use a dash. Use wildcard string expressions separated by commas to match event sources, included in the list of reported events. For Example, using This field does not support regular expressions. |
| Event Description Regex Filter | The name of the text string or regular expression you would like to look for in the Description field of the event. For more information see Regular expressions. |