[ZBX-2837] Zabbix Agent identifies incorrectly the EVENT SOURCE from new eventing system log "Windows Eventing 6.0" Created: 2010 Aug 07 Updated: 2019 Aug 27 Resolved: 2019 Aug 27 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Agent (G) |
Affects Version/s: | 1.9.0 (alpha) |
Fix Version/s: | None |
Type: | Incident report | Priority: | Major |
Reporter: | Oleksii Zagorskyi | Assignee: | Unassigned |
Resolution: | Won't fix | Votes: | 0 |
Labels: | eventlog, logmonitoring, windows | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
newest version of Windows (windows 7, 2008 server, maybe Vista also) |
Attachments: | 1.1.win7_event_source.png 1.2.win7_event_source.png 1.3.win7_event_source_in_Zab.png 2.1.win7_event_source.png 2.2.win7_event_source_in_Zab.png 3.1.win7_event_source_Filtering_names.png |
Description |
For me it is not yet a problem, but I decided to publish it with the greatest variety of examples that would have had in mind was once and can be corrected. I made two series of screenshots from Windows 7 (same as a 2008 server) for clarity.
Perhaps this problem should be considered together with |
Comments |
Comment by richlv [ 2010 Aug 09 ] |
so it's a provider name vs service name issue, i guess |
Comment by richlv [ 2015 Jan 05 ] |
|
Comment by Vladislavs Boborikins (Inactive) [ 2019 Aug 27 ] |
Hello, Since this version of Zabbix is no longer supported, we've decided not to prioritize this bug for the near future and close the issue with "Won't fix" resolution. Please let us know if this decision should be reconsidered. Regards |