PRTG Manual: Event Log (Windows API) Sensor
Important Notice |
---|
This sensor might not work anymore after Windows updates of June 2021. For more information, see the Knowledge Base: My Event Log (Windows API) sensors fail after installing Windows updates. What can I do? |
The Event Log (Windows API) sensor monitors Event Log entries via the Windows application programming interface (API).
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Event Log (Windows API)
- French: Journal des événements (API Windows)
- German: Ereignisprotokoll (Windows API)
- Japanese: イベントログ(Windows API)
- Portuguese: Log de eventos (Windows API)
- Russian: Журнал событий (API Windows)
- Simplified Chinese: 事件日志 (Windows API)
- Spanish: Registro de eventos (Windows API)
- This sensor has a very high performance impact. We recommend that you use no more than 50 of this sensor on each probe.
- This sensor supports IPv6.
- Knowledge Base: My Event Log (Windows API) sensors fail after installing Windows updates. What can I do?
- Knowledge Base: My Event Log sensor ignores changes in the event log. What can I do?
- Knowledge Base: How can I configure sensors using speed limits to keep the status for more than one interval?
You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. By default, PRTG shows this name in the device tree, as well as in alarms, logs, notifications, reports, maps, libraries, and tickets.
|
Parent Tags |
The tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Windows API Event Log Specific
Setting |
Description |
---|---|
Log File |
Specify the log file that this sensor monitors. The Windows event log provides several log files:
|
Setting |
Description |
---|---|
Event Type |
Specify the type of event that this sensor processes:
|
Filter by Source |
Filter all events for a certain event source:
|
Filter Type |
This setting is only visible if you enable Filter by Source above. Select the filter type:
|
Match String (Event Source) |
This setting is only visible if you enable Filter by Source above. Enter an event source that you want to filter for. Depending on the kind of filter, the sensor either processes the event source (Include filter option) or it does not process it (Exclude filter option). Enter a string. |
Filter by ID |
Filter all events for a certain event ID:
|
Filter Type |
This setting is only visible if ID filtering is On above. Select a filter type:
|
Match Values (Event ID) |
This setting is only visible if you enable Filter by ID above. Enter an event ID that you want to filter for. Depending on the kind of filter, the sensor either processes the event ID (Include filter option) or it does not process it (Exclude filter option).
|
Filter by Category |
Filter all events for a certain event category:
|
Filter Type |
This setting is only visible if you enable Filter by Category above. Select a filter type:
|
Match String (Event Category) |
This setting is only visible if you enable Filter by Category above. Enter a category that you want to filter for. Depending on the kind of filter, the sensor either processes the event category (Include filter option) or it does not process it (Exclude filter option). Enter a string. |
Filter by User |
Filter all received events for a certain event user:
|
Filter Type |
This setting is only visible if you enable Filter by User above. Select a filter type:
|
Match String (Event User) |
This setting is only visible if you enable Filter by User above. Enter a user name that you want to filter for. Depending on the kind of filter, the sensor either processes the event user (Include filter option) or it does not process it (Exclude filter option). Enter a string. |
Filter by Computer |
Filter all received events for a certain event computer:
|
Filter Type |
This setting is only visible if you enable Filter by Computer above. Select a filter type:
|
Match String (Event Computer) |
This setting is only visible if you enable Filter by Computer above. Enter a computer name that you want to filter for. Depending on the kind of filter, the sensor either processes the event computer (Include filter option) or it does not process it (Exclude filter option). Enter a string. |
Filter by Message |
Filter all received events for a certain event message:
|
Filter Type |
This setting is only visible if you enable Filter by Message above. Select a filter type:
|
Match String (Event Message) |
This setting is only visible if message filtering is On above. Enter a message that you want to filter for. Depending on the kind of filter, the sensor either processes the event message (Include filter option) or it does not process it (Exclude filter option). Enter a string.
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status |
New Records |
The number of new records
|
KNOWLEDGE BASE
My Event Log (Windows API) sensors fail after installing Windows updates. What can I do?
My Event Log sensor ignores changes in the event log. What can I do?
How can I configure sensors using speed limits to keep the status for more than one interval?
What security features does PRTG include?