Performance Data Handling

The boom solution supports the submitting of custom performance data from management plug-ins. All the submitted data gets stored centrally on the boom Server. Every registered class creates a separate table in the BOOM_PERF database. The integrated HTTP server includes a lightweight reporting engine.

Required Steps

A MPI must first register a performance class declaration with the boomperfreg script.
Usage: 

	  boomperfreg full/path/to/file.spec
Specification file format:
	  CLASS <className>
	  
	  <fieldname1> = <positionNumber>
	  BOOM_DATATYPE DOUBLE
	  
	  <fieldname2> = <positionNumber>
	  BOOM_DATATYPE BIGINT
	  
	  <fieldname3> = <positionNumber>
	  BOOM_DATATYPE VARCHAR 128
	  
	  ...
Supported types:
  • DOUBLE - the main type for performance values
  • BIGINT - represents long values (can be used for time)
  • VARCHAR <size> - any string values

After the specification file was processed by the Agent, the MPI can submit the performance data by using the boomperfstore script.
Usage: 

	  boomperfstore <classname> <values separated by space>
If the specification file is not registered, the submitting of performance data will be rejected. If the number of submitted values is different from the number of fields that are registered with spec file - the submitting of performance data will also be rejected.

The boom Server automatically alters the appropriate database table if a new version of the class specification was submitted by any system. But the table keeps the old field untouched and adds only not existing fields from the new registered specification. This allows to store data from multiple systems even if they are operating with different versions of the performance class.