GUI performance monitoring issues

The sensor gets the performance data for the collector. The collector application that is called pmcollector runs on every GUI node to display the performance details in the GUI. A sensor application is running on every node of the system.

If GUI is not displaying the performance data, the following might be the reasons:

Collectors are not enabled
Sensors are not enabled
NTP failure

Collectors are not enabled

Do the following to verify whether collectors are working properly:

Issue systemctl status pmcollector on the GUI node to confirm that the collector is running.
If collector service is not started already, start the collector on the GUI nodes by issuing the systemctl restart pmcollector command. Depending on the system requirement, the pmcollector service can be configured to be run on the nodes other than GUI nodes. You need to verify the status of pmcollector service on all nodes where collector is configured.
If you cannot start the service, verify its log file that is located at /var/log/zimon/ZIMonCollector.log to see whether it logs any other details of the issues related to the collector service status.
Use a sample CLI query to test if data collection works properly. For example:
```
mmperfmon query cpu_user
```

Note: After migrating from release 4.2.0.x or later to 4.2.1 or later, you might see the pmcollector service critical error on GUI nodes. In this case, restart the pmcollector service by running the systemctl restart pmcollector command on all GUI nodes.

Sensors are not enabled

The following table lists sensors that are used to get the performance data for each resource type:

Table 1. Sensors available for each resource type
Resource type	Sensor name	Candidate nodes
Network	Network	All
System Resources	CPU	All
	Load
	Memory
NSD Server	GPFSNSDDisk	NSD Server nodes
IBM Spectrum Scale™ Client	GPFSFilesystem	IBM Spectrum Scale Client nodes
	GPFSVFS
	GPFSFilesystemAPI
NFS	NFSIO	Protocol nodes running NFS service
SMB	SMBStats	Protocol nodes running SMB service
SMB	SMBGlobalStats	Protocol nodes running SMB service
CTDB	CTDBStats	Protocol nodes running SMB service
Object	SwiftAccount	Protocol nodes running Object service
	SwiftContainer
	SwiftObject
	SwiftProxy
Transparent Cloud Tiering	MCStoreGPFSStats	Cloud gateway nodes
	MCStoreIcstoreStats
	MCStoreLWEStats
Capacity	DiskFree	All nodes
	GPFSFilesetQuota	Only a single node
	GPFSDiskCap	Only a single node

Do the following to verify whether sensors are working properly:

Confirm that the sensor is configured correctly by issuing the mmperfmon config show command. This command lists the content of the sensor configuration that is located at /opt/IBM/zimon/ZIMonSensors.cfg.
The configuration must point to the node where the collector is running and all the expected sensors must be enabled. An enabled sensor has a period greater than 0 in the same configuration file. After the configuration file is updated, the pmsensor service needs to be restarted.
Issue systemctl start pmsensors to start the service if it is stopped.

If sensors and collectors are properly configured and enabled, you can issue the mmperfmon and mmpmon commands to see whether performance data is really generated.

You can query the data displayed in the performance charts through CLI as well. For more information on how to query performance data displayed in GUI, see Querying performance data shown in the GUI through CLI.

NTP failure

The performance monitoring fails if the clock is not properly synchronized in the cluster. Issue the ntpq -c peers command to verify the NTP state.