FillDB Perf Log Parser

Could someone please explain how to use the BESPerfLogParser tool? I’ve followed all of the docs I could find but I keep getting a PERL error when it the tool is run. My root server is 9.2.8.74 running on Win2012R2 and I keep getting the error below:

Can’t use string ("<Path to BES Server>") as a HASH ref while “strict refs” in use at /<Path to .exe>\BESPerfLogParser-3.0.3.40.exe>BESTools/Registry.pm line 61, line 165.

From what I understand the tool reads the FillDB PerformanceDataPath from the registry to get the location of the FillDB perf log but it results in the same or similar error as above whether it is run from the same folder or outside of it.

Any help would be appreciated.

Isn’t it obvious? :innocent: You can’t run it on the BES server. Place the tool and a copy of FillDBPerf.log in the same folder on your client. Then run it with no switches. It will create a text file and a csv file. Now whether the information indicates your systems is running well or not is another mystery.

2 Likes

Yeah. I eventually figured it out.

Hi, I get same error, even if I run the tool on a machine where BigFix is not installed. Any clue ?

@arnaud, did you ever figure this out. I know this has been several years but I am getting the same error no matter if I try running this tool from the root server or regular client.

My resolution was to use another tool. I ended up using MXFillDBPer tool within the MXTookit from https://bigfix-mark.github.io/Tools/MXToolkit.zip. I learned about this toolkit from https://bigfix-mark.github.io/Docs/MX%20Performance%20Toolkit%20for%20BigFix%20v10.pdf.

1 Like

@arnaud, Thank you. That is the same tool I found, and it worked like expected.