Supported Metrics and Default Monitoring Configuration

Supported Metrics

The following tabs represent the Metric Category of HPE Performance Cluster Manager

Metric Category	Native Type	Name	Display Name	Units	Description	Metric Group
HPC Node	hpc_node_nfsMounts_Available	HPC Node NFS Mounts Available	Usage	count	Provides the count of available NFS Mounts	nfsStats
	hpc_node_bond_err_in	HPC Node Bonded Network Interface Errors In	Usage	Errors per Sec	Provides the count of input errors on Bonded Network Interface	networkStatistics
	hpc_node_bond_err_out	HPC Node Bonded Network Interface Errors out	Usage	Errors per Sec	Provides the count of output errors on Bonded Network Interface	networkStatistics
	hpc_node_bond_in	HPC Node Bonded Network Interface In traffic	Usage	MBps	Provides the count of input traffic on Bonded Network Interface	networkStatistics
	hpc_node_bond_out	HPC Node Bonded Network Interface out traffic	Usage	MBps	Provides the out traffic on Bonded Network Interface	networkStatistics
	hpc_node_logins_count	HPC Node Logins Count	Usage	count	Provides the count of Node logins	sessionStats
	hpc_node_bufferCache_Utilization	HPC Node Buffer Cache Utilization	Performance	%	Provides the utilization of BufferCache	memoryAndCache
	hpc_node_cpu_freequency	HPC Node CPU Freequency	Performance	MHz	Provides the Freequency of CPU	cpuStats
	hpc_node_cpu_load	HPC Node CPU Load	Performance	%	Provides the CPU load	cpuStats
	hpc_node_diskReads_Persec	HPC Node Disk Reads Per Sec	Performance	MBps	Provides the Disk Reads Per Sec	diskStatistics
	hpc_node_diskWrites_Persec	HPC Node Disk Writes Per Sec	Performance	MBps	Provides the Disk Writes Per Sec	diskStatistics
	hpc_node_memory_usage	HPC Node Memory Usage	Performance	%	Provides the used memory utilization	memoryAndCache
	hpc_node_network_trafficIn	HPC Node Network Traffic In	Performance	MBps	Provides the usage of network traffic In	networkStatistics
	hpc_node_network_trafficOut	HPC Node Network Traffic Out	Performance	MBps	Provides the usage of network traffic Out	networkStatistics
	hpc_node_pageCache_Usage	HPC Node Page Cache Usage	Performance	%	Provides the usage of Page Cache	memoryAndCache
	hpc_node_processMemory_usage	HPC Node ProcessMemory Usage	Performance	%	Provides the usage of Process Memory	memoryAndCache
	hpc_node_swapAvailable_mb	HPC Node Available Swap Memory	Availability	MB	Provides the available swap memory	swapSpace
	hpc_node_uptime_InDays	HPC Node Uptime In Days	Availability	Days	Provides the Uptime in Days	nodeRuntime
	hpc_node_swapMemory_usage	HPC Node Swap Memory Usage	Performance	%	Provides the usage of swap memory	swapSpace

Default Monitoring Configurations

HPE Performance Cluster Manager (HPCM) has default Global Device Management Policies, Global Templates, Global Monitors and Global metrics in OpsRamp. You can customize these default monitoring configurations as per your business use cases by cloning respective global templates and global Device Management Policies. OpsRamp recommends performing the below activity before installing the application to avoid noise alerts and data.

Default Global Device Management Policies

You can find the Device Management Policy for each Native Type at Setup > Resources > Device Management Policies. Search with suggested name in global scope. Each Device Management Policy follows below naming convention:

{appName nativeType - version}

Example: hpe-performance-cluster-manager HPC Node - 1 (i.e, appName = hpe-performance-cluster-manage, nativeType = hpcm Node, version = 1)

Default Global Templates
You can find the Global Templates for each Native Type at Setup > Monitoring > Templates. Search with suggested names in global scope. Each template follows below naming convention:
{appName nativeType 'Template' - version}
Example: hpe-performance-cluster-manager HPC Node Template - 1 (i.e, appName = hpe-performance-cluster-manager, nativeType = HPC Node, version = 1)
Default Global Monitors
You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested name in global scope. Each Monitors follows below naming convention:
{monitorKey appName nativeType - version}
Example: HPC Node Monitor hpe-performance-cluster-manager HPC Node - 1(i.e, monitorKey = hpcm-node Monitor, appName = hpe-performance-cluster-manager, nativeType = HPC Node, version = 1)