Re:Sysmon – Log system activity to the Windows event log
by pestaa on Saturday August 09, 2014 @08:03AM
(#8156738)
It's not a deal-breaker, but <key>value</key> would indeed be nicer.
Re:Sysmon – Log system activity to the Windows event log
by LoneWolf on Saturday August 09, 2014 @09:29AM
(#8156849)
For a human to read maybe, but for some generic parsing where there are many diferent keys, I would say <data Name="key">value</data> is indeed better, also makes an XSD easier to create, if needed.
Re:Sysmon – Log system activity to the Windows event log
by michh on Saturday August 09, 2014 @03:30PM
(#8157806)
That definitely goes towards the "good reason not to use XML" part of what I said, imo ;)
Re:Sysmon – Log system activity to the Windows event log
by windowsworkstoo on Saturday August 09, 2014 @06:08PM
(#8158144)
This is a limitation of the way ETW does structured logging, rather than a design decision in sysmon itself.
Re:Sysmon – Log system activity to the Windows event log
by karlmdavis on Saturday August 09, 2014 @09:10AM
(#8156825)
I can understand why they wouldn't have wanted to create an XSD covering all of the possible keys.
Re:Sysmon – Log system activity to the Windows event log
by kryptiskt on Saturday August 09, 2014 @10:04AM
(#8156896)
Free-form tag names invariably leads to conflicts with previously defined tags that are used for other purposes. I don't see how not wanting an unbounded number of different tags would be antithetical to use of XML.
If there's a good reason for it, it's just as much of a good reason XML isn't suitable for what you're trying to do.