eventlog event logs Application Error.xml
result.png
trigger-expression.png
[ZBX-20559] Windows Event Log problem closes without a reason Created: 2022 Feb 08 Updated: 2022 Feb 22 Resolved: 2022 Feb 22 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Server (S) |
| Affects Version/s: | 5.0.19, 5.4.10 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Minor |
| Reporter: | Aigars Kadikis | Assignee: | Aigars Kadikis |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
eventlog event logs Application Error.xml
result.png
trigger-expression.png
|
| Description |
|
The goal is to analyze windows server in retrospect (without using "skip" option) and gather all Windows event logs if there is "Application Error" entry in the Windows Event Viewer. Generate event per each entry. This will require "PROBLEM event generation mode": "Multiple" Trigger configuration:
As a result, it starts to close events automatically:
Template: With agent2 5.0.19 and agent2 5.4.10 |
| Comments |
| Comment by Alexander Vladishev [ 2022 Feb 09 ] |
|
In this case, all open problems will be closed if the server receives an event log entry with a severity other than 4. Please attach received history for this item. |
| Comment by Aigars Kadikis [ 2022 Feb 22 ] |
|
Works correctly. Needed to switch "OK event generation: None" to accomplish desired scenario. |
