[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: PNG File 1.1.win7_event_source.png     PNG File 1.2.win7_event_source.png     PNG File 1.3.win7_event_source_in_Zab.png     PNG File 2.1.win7_event_source.png     PNG File 2.2.win7_event_source_in_Zab.png     PNG File 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.
I tried to capture the maximum detail for analysis.
Briefly describe the problems were noticed:

  • For many events at the beginning of the text is appended text "Microsoft-windows-" ("Microsoft-windows-Kernel-Power"). This is probably a special case of the next situation;
  • Some are determined entirely from another undisclosed location ("DNS client Events").
  • The source is not taken from the correct place and does not coincide with the original name in Windows ("Windows Media Player Network Sharing Service").

Perhaps this problem should be considered together with ZBX-2008



 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 ]

ZBX-9183 seems to be similar

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
Vladislavs

Generated at Fri Apr 26 03:45:42 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.