Distributed systems measurement database joins - Documentation for Visualizer 4.2.07
James Rogers
Most metric group dynamic tables contain at least two places for manual database joins. The first joins the static table to the dynamic table. The second joins the dynamic table to the interval table.
The following is a sample of Static table and Dynamic table:
Typically the static table INDEXX field links to the first field in the dynamic table.
The second join links the Detailed Metric data in the dynamic table to the interval table that describes the time frame in which the data was recorded.
The following is a sample of Dynamic Table and Interval table:
The dynamic table INTVL field links to the INDEXX field of the CAXINTVL table.
SQL statement building tips
Use the following guidelines when building SQL statements to run against the Visualizer database:
Perform consistency check
In some fields such as Node_id and Disk_name, you will see trailing data such as:
Node name 8[K&_x)pMz2For those tables where this exists, use the _alias field as the source of your queries. For example, use:
where node_alias = 'nodename'
Avoid -1 values
If you come across a metric that has a value of minus one (-1), this means that the value was not available or not applicable. You may refine your queries to exclude these values from your calculations. For example, use:
where metric.value >= 0This can make things a little more difficult when dealing with multiple metrics. Fortunately only a relatively small number of metrics use this N/A value.
Related topic