{"id":309,"date":"2017-10-17T11:03:56","date_gmt":"2017-10-17T11:03:56","guid":{"rendered":"http:\/\/eventlogxp.com\/blog\/?p=309"},"modified":"2017-10-17T11:06:21","modified_gmt":"2017-10-17T11:06:21","slug":"the-fastest-way-to-filter-events-by-description","status":"publish","type":"post","link":"https:\/\/eventlogxp.com\/blog\/the-fastest-way-to-filter-events-by-description\/","title":{"rendered":"The fastest way to filter events by description"},"content":{"rendered":"

Filtering events by description is one of the most asked questions to us. Some time ago I wrote an article<\/a> devoted to this problem.<\/p>\n

Recently we had to check all events in the security log linked with a certain file (let’s say, it’s winword.exe, C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE). The easiest solution was to use Filter command and type file name in the “Text in description” line.<\/p>\n

\"Filter<\/a><\/p>\n

Commonly this works fine, but it scans all records in the log, forms event description for each event and looks for this phrase in the description. Forming event descriptions may require loading extra modules from the target computer (or a computer you designated as a description server) to load the description template. And although Event Log Explorer caches and reuses description templates, such filtering may take long time on large logs.<\/p>\n

As a rule, security log stores file names, process names and other details in separate XML elements under \u00a0EventData and all these elements are named “Data”.<\/p>\n

\"XML<\/a><\/p>\n

So, we can make an XPath query to a log which compares each Data element with our search string. This query will look like:<\/p>\n

*[EventData[Data=\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]]<\/pre>\n
To apply this filter, open Security event log, select View->XML Query, type your XPath expression and click OK.<\/p>\n
\"XPath<\/a><\/p>\n
It executes swiftly and doesn’t load network when connecting a remote computer.<\/p>\n
But what about the other logs? Many Windows events doesn’t have EventData element, but have UserData (some events have DebugData, BinaryEventData, or ProcessingErrorData instead). UserData commonly has an extra level of XML elements, so to query event by UserData, we should use the following XPath request:<\/p>\n
*[UserData[*[*=\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]]]<\/pre>\n
And what if you want to check for the same file name in several logs, e.g. in Security, System and Application logs? It can be also done with one XML query:<\/p>\n
<QueryList>\r\n  <Query Id=\"0\">\r\n    <Select Path=\"Security\">*[EventData[Data=\r\n\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]] or \r\n    *[UserData[*[*=\r\n\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]]]\r\n    <\/Select>\r\n\r\n    <Select Path=\"System\">*[EventData[Data=\r\n\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]] or \r\n    *[UserData[*[*=\r\n\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]]]\r\n    <\/Select>\r\n\r\n    <Select Path=\"Application\">*[EventData[Data=\r\n\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]] or \r\n    *[UserData[*[*=\r\n\"C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE\"]]]\r\n    <\/Select>\r\n  <\/Query>\r\n<\/QueryList><\/pre>\n
Here is the result of this query on my machine:<\/p>\n
\"XML<\/a><\/p>\n
Advantages of this method<\/h4>\n
Such XML query provides great performance and works not only with Event Log Explorer, but with Windows Event Viewer or other event log programs which support XML queries.<\/p>\n
Some applications and services logs don’t display all the information about event in the description, but still store their details under UserData or EventData elements (I described one of such logs in this article<\/a>). So, filtering by description won’t work for such events,\u00a0 but the XPath queries will.<\/p>\n
Limitations<\/h4>\n
Although this approach lets you filter quickly by description details, it is limited by XPath 1.0 implementation for event logs. E.g. you can use only 3 functions: “position”, “Band” (binary and) and “timediff”. Function “contains” is not supported, so it’s impossible to filter just by filename (winword.exe). If you need to filter just by file name, you should use general filter by description.<\/p>\n
Can we do something to bypass these limitations? I think so. Filtering by description parameters during log loading stage (and without forming descriptions) should work faster than general filter by description and it will be more flexible than Xpath. But it would be really great if Microsoft extends XPath functionality for event logs.<\/p>\n\"Facebook\"<\/a>\"twitter\"<\/a>\"reddit\"<\/a>\"pinterest\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"
Filtering events by description is one of the most asked questions to us. Some time ago I wrote an article devoted to this problem. Recently we had to check all events in the security log linked with a certain file (let’s say, it’s winword.exe, C:\\Program Files (x86)\\Microsoft Office\\root\\Office16\\WINWORD.EXE). The easiest solution was to use Filter command and type file name in the “Text in description”\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":315,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[19,34,35],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/309"}],"collection":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/comments?post=309"}],"version-history":[{"count":6,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/309\/revisions"}],"predecessor-version":[{"id":320,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/309\/revisions\/320"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/media\/315"}],"wp:attachment":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/media?parent=309"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/categories?post=309"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/tags?post=309"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}