Tag Archives: PHC

Revision 527 – Improved FileSystem Layout Detection

Posted on by

internal: the detection of filesystem layout and file relative locations was all twisted, and was flakey. So I’m ripping it out. It’s mostly refactored, but in order to leverage it sooner, there are currently both methods active. The flakey one will finish dying very soon, but in the meantime, only most of the code benefits from this structure change rather than all of it.

The way I’m doing it now is a straight Booch-ian method of taking multiple objects and using them to encapsulate the logic. They are interchangeable. The most applicable will be chosen by — you guessed it — voting. Whichever one looks most likely will be used. This allows me to abstract off discovery of pathnames and locations as they change from live server, PortalLogs, and database backup without huge changes in code and whackloads of if/else loops.

The behavior I wanted to leverage more quickly is the reading of summarymon log to check performance at the database insertion side.

Revision 492 – second skew-check

Posted on by

It seems that someone is creating Demo Databases rather than use mine (which are cleaned up by Nick).

They’re broken. Specifically, they have extra data appended at some point. HINT: if the data in your five-minute summary ends at 2011-11-16, but your last interval is 2012-04-17, you have the broken one.

PHC now detects that, using both the packages and the final summary.

Revision 476 – Added Auto Mode to PHC

Posted on by

For revision 476, I wrote “made PHC “do the right thing” a bit better by dropping out some config in the bat file and activating an “auto” mode; may have issues in a “-h uri” mode”

In short, there it is: the PHC becomes “Automatic-er” and allows me to be lazier. Avoiding possible user-error is merely a stretch-goal 🙂

Consider the 7 characters:

PHC.BAT

What this does is:

  1. find your java.exe in a list of 12 most likely places
  2. if PHC-XLSX.jar is available, use it; otherwise, use PHC.jar
  3. runs it in “-A” or “–auto” mode

Auto Mode

Auto Mode simply does the smarter things for you, so that fewer choices are necessary:

  1. if PHC-XLSX.jar has enabled XLSX creation, build phc.xlsx
  2. if any OUIs are missing, look them up, and create phc-OUISignatureList.xml which can be used as the basis of edits to OUISignatureList.xml
  3. if VMs are present, and some HBAs are not set, produce phc-vm.csv which can define HBA speeds based on having all HBAs under ProbeSW
  4. pri