Analyzing Event Log Entries in PowerPivot
PowerPivot for Excel is a great analysis tool for information workers. You can import data from any supported data source in your environment or from Azure DataMarket and then analyze that data with supercool Data Analysis Expressions (DAX), but who says PowerPivot is just for information workers? PowerPivot is for everybody! So, why not analyze computer information if you happen to be an IT pro?
If you are an IT pro, you might find it interesting to analyze the Windows Event Log. It’s a great source of valuable information. You might be able to find certain patterns of system errors or security incidents on your servers and workstations. So, let’s load event log data into PowerPivot. One way to accomplish this is to export the data into a CSV file and then import that CSV file into PowerPivot.
Here are the steps:
- Start Control Panel, and then in Category view, click System and Security, click Administrative Tools, and then double-click Event Viewer.
- Expand Windows Logs, right-click the desired log, such as System, click Save All Events As, and then in the Save As dialog box, under File Name, type a meaningful name, such as System, and under Save As Type, select CSV (Comma Separated) (*.csv). Click Save.
- Switch to the PowerPivot window, and then under Get External Data, click on From Text.
- In the Table Import Wizard that appears, click Browse, and then in the Open dialog box, next to File Name, select Comma Separated Files (*.csv), and select the previously saved file. Click Open.
- Notice the data preview in the Table Import Wizard. Select the checkbox Use First Row As Column Headers and then click Finish.
And after removing some invalid characters from the Level heading and renaming the F6 column to Event Details (just right-click the headings and select Rename Column), the data is ready for analysis:
- Switch to the Excel window, and then on the PowerPivot ribbon, in the Report section, click on the little triangle underneath PivotTable. Select the option Chart and Table (Horizontal).
- In the Create PivotChart and PivotTable (Horizontal) dialog box, select Existing Worksheet, and then click OK.
- PowerPivot places an empty chart and an empty PivotTable on the worksheet. Select the chart and then, in the PowerPivot Field List to the right, drag the following fields to the field areas:
Field Area |
Fields |
∑ Values: |
Event Details (automatically changes to Count of Event Details) |
Axis Fields (Categories): |
Date and Time |
Slicers Vertical: |
Level, Event ID |
- On the Excel worksheet, click in the area of the PivotTable, and then in the PowerPivot Field List drag the fields Source and Event Details onto the Row Labels field area.
- On the Excel worksheet, right-click the column that contains the PivotTable, such as column D, and click Column Width. Under Column Width, type 66, and then click OK.
- Right-click the column that contains the PivotTable again and click PivotTable Options, and then in the PivotTable Options dialog box, clear the checkbox Autofit Column Widths On Update. Click OK.
- Right-click the column that contains the PivotTable one more time and click Format Cells. Switch to the Alignment tab, and then under Text Control, select the checkbox Wrap Text, and click OK.
- Test your solution by clicking on a slicer, such as on Information, Error, or Warning. Observe how the data in the chart and in the PivotTable changes, then save your work.
Of course, this is a very basic solution, yet it might nevertheless be useful. Let me know if you find these IT-pro scenarios interesting. In my next blog post, I’m planning to show you how to analyze performance data in PowerPivot. Stay tuned!
Comments
- Anonymous
May 31, 2011
Fantastic example. I am planning to use Perfmon data for analysis. :) - Anonymous
May 31, 2011
Hi,There is a problem in importing perfmon (CSV) file. The problem is in the header of the file. it has lot of "" in the header name. - Anonymous
June 01, 2011
Hi Ayyappan,are you importing event log data or is this data gathered via performance monitor? Assuming it's the latter, don't use the csv file option for that. You'll run into a number of issues. I'll discuss this in my next post. Plan is to post it in a couple of weeks... still need to write it. :-)Cheers,Kay - Anonymous
October 17, 2011
Hi Kay, I believe i speak in the name of many when I say that we are using every possible solution to data-mine those extremelly long and ugly CSV log files.It helped me exactly for the same purpose!Thank you again,C:Marius - Anonymous
May 15, 2013
is there a way to automate this? i'm doing it with log parser but looking for another way. importing the data into SQL and then working on it in SQL is pretty slow. looking at analysis services