login vsi company logo login vsi company logo 250x40

 

Get the best possible VDI performance, density and availability with Login VSI
Our Solutions

  • Home
  • Blog
  • Login VSI
  • Cleaning up esxtop log files using PowerShell - Login VSI Tips and Tricks

Cleaning up esxtop log files using PowerShell - Login VSI Tips and Tricks

Cleaning up esxtop log files using PowerShell - Login VSI Tips and Tricks

Every now and then when doing large scale tests using Login VSI or collecting live performance data I use VMware's esxtop tool to give me a detailed insight to what’s going on at the host. While esxtop provides great insights, sometimes it’s just a little bit too much information. This got me thinking, how can I quickly sanitize the log file so it only contains information that is actually relevant for me at this moment?

And, of course, the first thing that comes to mind is a few lines of PowerShell. I simply import the csv file collected using esxtop and export it again containing only the columns of information I like. So let’s import the esxtop logfile using the Import-CSV command, select the data I like using select-object and throw it out again using export-csv.

cleaning up esxtop log files using powershell error

Hmmm, what’s happening here? This should have been a fairly straight forward. Analyzing it a bit further, I found out that this is because there is a comma ending every line.

cleaning up esxtop log files using powershell error comma

Luckily PowerShell allows me to fix that before I feed the content to import-csv. While experimenting, I figure at this point it’s probably best to create a simple script that does the following:

  • Point to the esxtop log that I would like to filter
  • Import the “broken” csv file
  • Remove the last character from every line
  • Import the “fixed” CSV file
  • Select the counters of my choice
    • *\Physical Cpu(_Total)\% Util Time
    • *\Physical Disk Adapter(vmhba0)\Commands/sec
    • *\Physical Disk Adapter(vmhba0)\Reads/sec
    • *\Physical Disk Adapter(vmhba0)\Writes/sec
  • Write it to a new file (export.csv)
  • Clean up
Write-Host Select file
$fd = New-Object system.windows.forms.openfiledialog
$fd.MultiSelect = $false
$fd.showdialog()
$fd.filenames
Write-Host Read file
$lines=@()
$text = Get-Content -Path $fd.filenames
$text | %{ $lines += $_.SubString(0,$_.Length-1) }
$FixedFilename = $fd.filenames -replace ".csv", ".fixed"
$FilteredFilename = $fd.filenames -replace ".csv", ".filtered"
Write-Host Write fixed logfile
Set-Content -Path $FixedFilename -Value $Lines
Write-Host Read fixed logfile
$csv = import-csv -path $FixedFilename
Write-Host Write filtered logfile
$csv | select-object "*\Physical Cpu(_Total)\% Util Time", "*\Physical Disk Adapter(vmhba0)\Commands/sec", "*\Physical Disk Adapter(vmhba0)\Reads/sec", "*\Physical Disk Adapter(vmhba0)\Writes/sec" | export-csv  export.csv -notypeinformation
Write-Host Delete temp files
remove-item $FixedFilename 

For those of you who have their regional settings setup in a way that Excel does not require the comma fix, that’s great! Otherwise you can now live knowing that your log files will be a lot smaller :-).

Also, make sure to read this blog about PowerShell.

 


 

Start using Login VSI today

Our industry-standard software is built to help you avoid problems, lower costs and improve performance. Request a Quote or get your free Trial below, and benefit from our award-winning services.

Free Price Request  Your Free Trial

 


About the company Login VSI

The company Login VSI provides end-user performance insights for virtualized desktop and server-based computing environments. Enterprise IT departments use flagship product Login VSI (for load testing) and Login PI (for continuity testing) in all phases of their virtual desktop deployment—from planning to deployment to change management—to build and safeguard a good performance, a high availability, and (as a result) a good and consistent end-user experience. For more information about Login VSI or for a free test license contact us.

About the author

Mark Plettenberg (@markplettenberg) is a product manager of Login VSI and has played a critical role in the development and growth of Login VSI. Ask Mark about motorcycle mechanics and breaking/repairing anything and everything that has a power plug.


Tags: How-to, Login VSI, VMware, Load Testing, Best Practices, Support, Scripts

Popular Blogs

Login VSI officially recognized as an integration partner for WVD by Microsoft

Windows Virtual Desktop

I’m excited to share with you that as of this week Login VSI has officially been recognized as an integration partner for Windows Virtual Desktop (WVD) by Microsoft. Continue Reading
Join us at VMworld 2019 - Booth #866

Join us at VMworld 2019 - Booth #866

Join us at VMworld 2019 - Booth #866 Are you attending VMworld in San Francisco next week? Great, we are too! Continue Reading
State Of The Union Survey Results 2019

State of EUC Survey Results

State of EUC Survey Results At community site VDILIKEAPRO.com we recently surveyed almost 600 people who work in the End User Computing (EUC) industry with a focus on VDI and SBC. Continue Reading
Login VSI at VMworld 2019 - Our Debrief

VMworld 2019 - Our Debrief

VMworld 2019 It’s that time of the year again, we’ve just wrapped up VMworld US and it was great meeting many folks on the expo floor, vendor booths, sessions and of course for a drink in the evening. Continue Reading
Windows Virtual Desktop - Update - December 2019

Windows Virtual Desktop Enhanced in the Latest Update

Planning to move to Windows Virtual Desktop and/or Citrix Managed Desktop? A lot has already been written about Windows Virtual Desktop (WVD) in the last months and while I had my initial concerns on this service many people are suggesting that they are willing to move to a platform like WVD in the next two years. Continue Reading
Login VSI - Blog - 4 Things to Consider when Running Office 365 in the Cloud

4 Things to Consider when Running Office 365 in the Cloud

Recently a customer decided to move their entire VDI infrastructure into the cloud. The VDI environment was approximately 20,000 users. As you can imagine there are a lot of design decisions necessary to ensure the success of this migration. Continue Reading
Cookie Settings