{"id":569,"date":"2024-02-17T21:28:24","date_gmt":"2024-02-17T21:28:24","guid":{"rendered":"https:\/\/eventlogxp.com\/blog\/?p=569"},"modified":"2024-02-17T21:37:55","modified_gmt":"2024-02-17T21:37:55","slug":"extra-power-of-custom-columns","status":"publish","type":"post","link":"https:\/\/eventlogxp.com\/blog\/extra-power-of-custom-columns\/","title":{"rendered":"Extra power of custom columns"},"content":{"rendered":"

Approximately 10 years ago, we introduced custom columns in Event Log Explorer. This feature allows users to extract event details from the event description or event XML. Custom columns have significantly enhanced our customers’ ability to get more information from events, and we have continuously improved it across different versions. Previously, Event Log Explorer treated custom column values as text, which sometimes was insufficient for in-depth analysis. For example, in my article about tracking printer usage<\/a>, it was impossible to sort events by the number of pages.<\/p>\n

Since version 5.5, Event Log Explorer allows users to specify the type of custom values.<\/p>\n

Let\u2019s take the same printer usage problem and solve it using this new power.<\/p>\n

    \n
  1. Make sure that logging of Microsoft-Windows-PrintService\/Operational log is enabled on your print server and open it.<\/li>\n
  2. Set filter to Event ID = 307<\/li>\n
  3. Optionally hide unnecessary columns like Type, Event Id, Source, Category, User<\/li>\n
  4. Set custom columns as follows:
    \nColumn 1:
    \nColumn title: Printer user
    \nValue: {DATA[3]}
    \nTreat value as : Text
    \nColumn 2:
    \nColumn title: Printer
    \nValue: {DATA[5]}
    \nTreat value as: Text
    \nColumn 3:
    \nColumn title: Pages
    \nValue: {DATA[8]}
    \nTreat value as: Integer<\/li>\n<\/ol>\n

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

    As seen, you only need to set “Treat value as” to Integer for the last custom column. This will display events like the previous versions displayed, but now the Pages column is shown as an integer column.<\/p>\n

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

    This means that you can now sort by this column from lowest to highest value (or vice versa), not just alphabetically. You can also filter by this value (e.g., greater than or less than).<\/p>\n

    Furthermore, you can now create a summary table and calculate the total number of pages by every user. To do so, you will need to generate a new analytical report.<\/p>\n

    Select Advanced->Analytical reports<\/strong> from the main menu.<\/p>\n

    Then select Field List and move “Printer user” to the left area.<\/p>\n

    Select Field List again and move Pages to the central area.<\/p>\n

    Next, move Measures (1) into the top area.<\/p>\n

    This will create a summary table that looks like this:<\/p>\n

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

    Note that Event Log Explorer automatically calculates the sum of pages for each user because Sum is the default aggregative function for integer fields. However, you can change it to any other aggregative function if needed. For instance, if you want to get the average number of pages every user prints at once, expand Measures (1), right-click on Pages, select Properties, and in the Measure Editor dialog, change Sum to Average, then click OK.<\/p>\n

    As you can see, custom columns now offer enhanced capabilities for analyzing Windows event logs.<\/p>\n

    Get the latest version of Event Log Explorer<\/a> to leverage the full potential of custom columns right away!<\/p>\n\"Facebook\"<\/a>\"twitter\"<\/a>\"reddit\"<\/a>\"pinterest\"<\/a>\"linkedin\"<\/a>\"mail\"<\/a>","protected":false},"excerpt":{"rendered":"

    Approximately 10 years ago, we introduced custom columns in Event Log Explorer. This feature allows users to extract event details from the event description or event XML. Custom columns have significantly enhanced our customers’ ability to get more information from events, and we have continuously improved it across different versions. Previously, Event Log Explorer treated custom column values as text, which sometimes was insufficient for\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":574,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[41],"tags":[5,69,70],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/569"}],"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=569"}],"version-history":[{"count":2,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/569\/revisions"}],"predecessor-version":[{"id":575,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/posts\/569\/revisions\/575"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/media\/574"}],"wp:attachment":[{"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/media?parent=569"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/categories?post=569"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eventlogxp.com\/blog\/wp-json\/wp\/v2\/tags?post=569"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}