Using SQL to monitor applications, processes, networks, and servers with HEYMon and HEYMonSQL.

HEYMonSQL Monitoring with the table model

When you configure HEYMon to monitor parts of your enterprise, you are configuring HEYMon Jobs that will perform certain types of work known as a Job Type. Jobs, and the work they perform represent the core technology which comprises the HEYMon engine. If you want to do things with HEYMon, you have to be able to create and execute Jobs.
When you use HEYMonSQL to configure and execute Jobs, you have to match the taxonomy of SQL with the functionality of the HEYMon engine. To accomplish this, HEYMonSQL uses a table model, where each table in the model represents one of the HEYMon job types.
The HEYMon job types are documented in the HEYMon 3.7 Users Guide, and you will need to understand the properties of each job type to know how to configure it for HEYMon or HEYMonSQL.
But with HEYMonSQL and the table model, you can use SQL to describe all the tables (jobs) supported, and describe all the properties and options of that table (job type properties).
A Table in HEYMonSQL is the same as the description of a configured Job, or as the Job Type of the same name.
For example, there is an ErrorLog table in HEYMonSQL, which is the same as the ProcessErrorLogJob job type. We can use this HMSQL statement to get a list of all the supported tables in our configuration:

For any of the tables in list, we can see what values are required by describing the table.
We can use this HMSQL statement to get a list of all the properties for one of the tables:

<== Previous          Next ===>