...
Given the definition of the performance data export pipeline, the logical place to start looking when null values appear is at step 1. Find a file in /usr/local/omk/var/perf/<time_period>/<table>-<time_period>-node.nmis, view it in a text editor (like vi).
Is the null column name you are looking for defined in the file? (note, column names in this file can be re-mapped to different column names using the schema, so double check the schema for the name you should be looking for if you can't find it)
- No: If it is not defined it's likely that the model that the node uses either does not support the data or the export script hasn't been modified to add that information to the export (likely because it might not make logical sense to want to track that data for that model, eg, tracking cpu performance on your UPS)
- Yes: this means the data that was grabbed was not defined.
- Is thresholding turned on for this node? Check Nodes.nmis, search for the node name, look for 'threshold' => 'true'. To count the number enabled and disabled run these commands:
- grep -c "'threshold' => 'true'" /usr/local/nmis8/conf/Nodes.nmis
- grep -c "'threshold' => 'false'" /usr/local/nmis8/conf/Nodes.nmis
- Is NMIS running thresholding (either 'threshold_poll_cycle' => 'true', or with a separate nmis.pl type=threshold)?
- Can you find the value in the var/<node_name>-node.nmis file for the node?
- Is thresholding turned on for this node? Check Nodes.nmis, search for the node name, look for 'threshold' => 'true'. To count the number enabled and disabled run these commands:
...