You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows events have an eventData field, which contains data specific to the event type. The windows input in stanza currently parses this as a slice of strings, which it populates with the entry values. However, the entries can also have names, and in that case, it makes more sense for this to be a map.
swiatekm
changed the title
eventData for Windows event logs should be a map if possible
[pkg/stanza] eventData for Windows event logs should be a map if possible
Apr 3, 2023
@djaglowski I have a fix ready to go, so you can assign directly to me if you think the change is obvious enough. I think it's technically breaking, but realistically nobody was actually depending on this, as it's basically unusuable in its current state.
Component(s)
pkg/stanza
What happened?
Description
Windows events have an
eventData
field, which contains data specific to the event type. Thewindows
input in stanza currently parses this as a slice of strings, which it populates with the entry values. However, the entries can also have names, and in that case, it makes more sense for this to be a map.For example:
See here for reference.
Steps to Reproduce
Any use of the windowseventlog receiver will show the problem. I've included the output for the example above below.
Expected Result
I'd expect to get the following for the example above:
Actual Result
Collector version
All recent versions
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: