Adding or removing a sensor from an existing automated configuration

The performance monitoring system can be configured manually or through an automated process. To add a set of sensors for an automatic configuration, generate a file containing the sensors and the configuration parameters to be used.

The following example shows the file /tmp/new-pmsensors.conf that is used to add the following sensors:

A new sensor NFSIO, which is not activated yet (period=0).
Another sensor SMBStats, whose metrics are reported every second (period=1).

The restrict field is set to cesNodes so that these sensors only run on nodes from the cesNodes node class:

sensors = {
        name = "NFSIO"
        period = 0
        restrict = "cesNodes"
        type = "Generic"
},
{
        name = "SMBStats"
        period = 1
        restrict = "cesNodes"
        type = "Generic"
}

Ensure that the sensors are added and listed as part of the performance monitoring configuration. Run the following command to add the sensor to the configuration:

mmperfmon config add --sensors /tmp/new-pmsensors.conf

If any of the sensors mentioned in the file exist already, they are mentioned in the output for the command and those sensors are ignored, and the existing sensor configuration is kept. After the sensor is added to the configuration file, its configuration settings can be updated using mmperfmon config update command.

Run the following command to delete a sensor from the configuration:

prompt# mmperfmon config delete --sensors Sensor[,Sensor...]

Note: IBM Spectrum Scale version 4.2.2 has two new sensors: GPFSPool and GPFSFileset for the pmsensor service. If an older version of the IBM Spectrum Scale performance monitoring system is upgraded, these sensors are not automatically enabled. This is because automatically enabling the sensors might cause the collectors to consume more main memory than what was set aside for monitoring. Changing the memory footprint of the collector database might cause issues for the users if the collectors are tightly configured. For information on how to manually configure the performance monitoring system (file-managed configuration), see Manual configuration.