Additional event mapping from CA UIM Probes to CA Spectrum
casp1032
Till CA Spectrum 10.2, apart from events related to VMWare and servers, events from CA UIM were considered as generic events by CA Spectrum. As a result users were unable to create specific rules for those events due to lack of unique event codes. From the CA Spectrum 10.2.1 release those events are also to be mapped to unique event code so that you can customize them and manage the events raised on CA UIM more effectively.
Please see the tables below to see the mapping of events from the probes to unique event codes in CA Spectrum:
The SQL Server Monitoring (sqlserver) probe constantly monitors the internal performance and space allocation of SQL Server databases. The probe can run locally on the database server or it can be configured to run as a remote client. The probe feeds essential information that is based on predefined criteria to the UIM availability manager for appropriate alert notification, as required. An extensive range of checkpoints can be selected and individually scheduled to meet your monitoring requirements. The probe will run selected SQLs to extract vital information about your SQL Servers. The information is presented to database-administrator as alarms or reports.
Checkpoint Metric | Description | Metric Type | CA Spectrum Event ID | Units |
active_connection_ratio | Monitors the numbers of active connections. | 4.2:51 | 0x06330077 | Percent |
active_users | Monitors the number of users having an active transaction at the moment of snapshot. | 4.2:1 | 0x06330078 | Count |
agent_job_failure | Monitors failed agent jobs in a defined time interval. Note: This monitor does not generate a clear alarm, by default. You can change the value of the clear_alarms key to 1 , using the Raw Configure option, to generate the clear alarm. | 4.2:57 | 0x06330079 | Count |
alloc_space | Monitors allocated space. | 4.2:2 | 0x0633007a | Percent |
av_fragmentation | Monitors average fragmentation. | 4.2:3 | 0x0633007b | Percent |
average_waittime | Monitors average lock wait time interval in ms.
High wait time causes performance degradation, consider increase number of locks available or computer memory. | 4.2:4 | 0x0633007c | Milliseconds |
backup_status | Monitors in minutes, since last database backup has been taken.
For all databases that have never been backed up, this checkpoint returns -1 value. | 4.2:5 | 0x0633007d | Minutes |
blocked_users | Monitors the number of blocked users. | 4.2:48 | 0x0633007e | Count |
buf_cachehit_ratio | Percentage of pages found in the buffer cache without having to read from the disk. The ratio is the interval number of cache hits divided by the interval number of cache look-ups. Note : As reading from the cache is less expensive than reading from disk, you want this ratio to be high. Generally, you can increase the buffer cache hit ratio by increasing the amount of memory available to the SQL Server. | 4.2:6 | 0x0633007f | Percent |
check_dbalive | Attempts to connect to the server. This checkpoint cannot be deactivated and returns two values with which threshold comparison is done:
| 4.2:7 | 0x06330080 | State |
connection_memory | Monitors amount of memory in KB that is used to maintain connections to SQL Server. | 4.2:8 | 0x06330081 | Kilobytes |
database_count | Change in the number of databases on the server. | 4.2:9 | 0x06330082 | Count |
database_size | Monitors the database status value.
The status value is actually a combination of some configuration options and a status, therefore, there can be multiple values set simultaneously (such as "torn page detection" and "loading"). | 4.2:10 | 0x06330083 | Megabytes |
database_state | State of the sql_server database.
For example, the database can be in any one of the following states:
| 4.2:11 | 0x06330084 | State |
deadlocks | Monitors the number of deadlocks per second in an interval. Note: As deadlocks can cause severe performance penalty, count must be close to 0. Use trace 1204 or 1205 to identify the deadlocked resources and involved applications. Procedure such as sp_lock delivers useful information about locking. | 4.2:12 | 0x06330085 | Count/s |
differential_backup_status | Monitors time in minutes since last differential backup. | 4.2:50 | 0x06330086 | Minutes |
fg_free_space | Monitors the amount of free space in database file groups in percent. If there is at least one file with "unlimited" growth in a file group, the space in this file group is considered as 100 percent free. | 4.2:64 | 0x06330087 | Percent |
free_connections | Monitors percentage of free connections to SQL Server instance, specified by parameter 'user connections' ( the maximum value must be 32676). | 4.2:14 | 0x06330088 | Percent |
free_space | Monitors the amount of free space in data files in percentage.
Note: If there is at least one file with "unlimited" growth, the space in the whole database is considered as 100% free. If you are using file groups, this could be misleading; therefore, you must deactivate this checkpoint and use only the "fg_free_space" checkpoint. | 4.2:15 | 0x06330089 | Percent |
full_scans | Monitors the number of full table or index scans per second in interval. If this value is high (2-10), then you must analyze your queries. | 4.2:16 | 0x0633008a | Count/sec |
latch_waits | Monitors the number of latch requests in an interval that could not be granted immediately and has to go in wait state. Note: If this number is high, the system experiences a low cache hit ratio and is forced to perform physical I/O operations. Add more memory or increase bandwidth of your system. | 4.2:17 | 0x0633008b | Request/sec |
lock_memory | Monitors amount of allocated lock memory in KB. | 4.2:18 | 0x0633008c | Kilobytes |
lock_requests | Monitors number of lock requests per second in interval. | 4.2:19 | 0x0633008d | Requests/Sec |
lock_timeouts | Monitors number of lock-timeouts per second in interval with precision of 0.001sec | 4.2:20 | 0x0633008e | Count/sec |
lock_waits | Monitors number of locks waits per second in interval. | 4.2:21 | 0x0633008f | Count/sec |
locked_users | Monitors the number of users suspended by locks at a given moment. Also, the blocked user and its current SQL are displayed. | 4.2:22 | 0x06330090 | Count |
locks_used | Monitors percentage of used lock and lock owner blocks. | 4.2:23 | 0x06330091 | Percent |
log_cachehit_ratio | Monitors the percentage of pages found in the log cache without having to read from disk. The ratio is the interval number of cache hits divided by the interval number of cache look-ups.
Note : Reading from the cache is much consumes less resources than reading from disk. You want this ratio to be high. You can increase the log cache hit ratio by increasing the amount of memory available to the SQL Server. | 4.2:24 | 0x06330092 | Percent |
log_file_growths | Monitors the number of times in an interval the transaction log for the database has been expanded. If this happens often, you must consider re-sizing your log files. | 4.2:25 | 0x06330093 | Count |
log_file_shrinks | Monitors the number of times in an interval the transaction log for the database has been decreased. If this happens often, you must consider re-sizing your log files. | 4.2:26 | 0x06330094 | Count |
log_flush_waits | Monitors the number of commits per second waiting on the log flush in an interval. When commits are waiting for log flushes, the log device is usually the bottleneck. | 4.2:27 | 0x06330095 | Count/sec |
logfile_size | Monitors the size of transaction log in MB for at least one transaction log file with "unlimited" growth in a database. Note: For this checkpoint, wherever the given database is in the recovery or restore mode, no metric values are reported for given interval of execution. | 4.2:52 | 0x06330096 | Count |
logfile_usage | Monitors the amount of free space in transaction log in percentage. If there is at least one transaction log file with "unlimited" growth in a database, the space in transaction log is considered as 100 percent free. Note: For this checkpoint, wherever the given database is in the recovery or restore mode, no metric values would be reported for given interval of execution. | 4.2:28 | 0x06330097 | Percent |
logic_fragment | Monitors the number of cluster index pages that are out of order. Any number higher than 10% indicates external fragmentation. The index should be rebuilt. Note: Non-cluster indexes are not monitored because a table can have only one clustering sequence. | 4.2:29 | 0x06330098 | Percent |
login_count | Monitors the number of users having an open connection to the server at a given time | 4.2:30 | 0x06330099 | Count |
long_jobs | Monitors all jobs running longer than defined threshold in seconds. | 4.2:31 | 0x063300a0 | Count |
long_queries | Monitors all queries running longer than defined threshold in seconds. | 4.2:32 | 0x063300a1 | None |
mirror_sqlinstance | Monitors availability of SQL server instance hosting the mirror database. | 4.2:55 | 0x063300a2 | State |
mirror_state | Monitors mirror database state. | 4.2:53 | 0x063300a3 | State |
mirror_witness_server | Monitors state of the witness server in the database mirror session. | 4.2:54 | 0x063300a4 | State |
optimizer_memory | Monitors amount of memory in KB that is used for SQL optimizer. | 4.2:33 | 0x063300a5 | Kilobytes |
page_reads | Monitors the number of physical database page-reads that are issued per second in an interval. Note: Since physical I/O is expensive, you can minimize the cost, either by using a larger data cache, intelligent indexes, more efficient queries, or by changing the database design. | 4.2:34 | 0x063300a6 | Counts/sec |
page_writes | Monitors the number of databases page-writes that are issued per second in an interval.
Note: Page-writes are generally expensive. Reducing page-write activity is important for optimal tuning. One way to do this is to ensure that you do not run out of free buffers in the free buffer pool. If you do, page-writes occurs while waiting for an unused cache buffer to flush. | 4.2:35 | 0x063300a7 | Counts/sec |
scan_density | Monitors the ratio between the best number of extents to the actual number of extents. It should be near 100 per cent. Lower number indicates external fragmentation and the object must be reorganized. | 4.2:36 | 0x063300a8 | Ratio |
server_cpu | Monitors percentage of CPU usage by SQL Server instance in interval. | 4.2:37 | 0x063300a9 | Percent |
server_io | Monitors percentage of I/O busy for SQL Server instance in interval. | 4.2:38 | 0x063300aa | Percent |
server_startup | Number of days the database server is up and running. | 4.2:39 | 0x063300ab | Days |
suspect_pages | Monitors suspect pages logged for databases. | 4.2:56 | 0x063300ac | Gauge |
sqlcache_memory | Monitors amount of memory in KB that is used for SQL statement cache. | 4.2:40 | 0x063300ad | Kilobytes |
table_space | Monitors amount of space (in KB/MB) reserved for a particular table in a database. This checkpoint can be used to control the size of fast growing tables. | 4.2:41 | 0x063300ae | Kilobytes |
total_memory | Monitors total amount of dynamic memory (in KB) that the server uses currently. | 4.2:42 | 0x063300af | Kilobytes |
transaction_backup_status | Sends QoS and Alarms for those databases that are running in full or bulk-logged recovery mode. Note : This checkpoint does not send QoS and Alarms for databases that are running in simple recovery mode. | 4.2:49 | 0x063300b0 | Minutes |
transactions | Monitors number of transactions per second in interval. | 4.2:43 | 0x063300b1 | Transactions/sec |
user_cpu | Monitors percentage of CPU usage by user in interval. Note: The checkpoint user_cpu reports $spid.$hostid in the QoS target. This results in the creation of new data series for each new $spid or $hostid . CA recommends disabling the QoS for this checkpoint. | 4.2:44 | 0x063300b2 | Percent |
user_waits | Monitors time in seconds for session spent waiting for a lock and length of blocking. Note: You can add schedules in the Exclude and Include lists. The match expression, which is added will be executed in the given time period mentioned in the schedule. | 4.2:45 | 0x063300b3 | Seconds |
workspace_memory | Monitors amount of memory in KB that is used for executing processes such as hash, sort, bulk copy, and index creation operations. | 4.2:46 | 0x063300b4 | Percent |
ls_primary_status | Monitors collective status of agents for the primary log shipping database. This checkpoint must run from primary server or monitor server. The status can be as follows:
| 4.2:58 | 0x063300b5 | Status |
ls_time_since_last_backup | Monitors time in minutes since last backup. | 4.2:60 | 0x063300b6 | Minutes |
ls_secondary_status | Monitors collective status of agents for the secondary log shipping database. This checkpoint must run from secondary server or monitor server. The status can be as follows:
| 4.2:59 | 0x063300b7 | Status |
ls_time_since_last_copy | Monitors time in minutes since last copy. | 4.2:61 | 0x063300b8 | Minutes |
ls_time_since_last_restore | Monitors time in minutes since last restore. | 4.2:62 | 0x063300b9 | Minutes |
ls_last_restored_latency | Monitors time in minutes since last restored latency. | 4.2:63 | 0x063300ba | Minutes |
fg_freeSpace_with_avail_disk | Monitors the amount of free disk space in database file groups in %. Free space for file groups (with auto growth enabled) is calculated after considering the available disk size on which the file group is located.
Notes:
| 4.2:64 | 0x063300bb | Percent |
logfile_usage_with_avail_disk | Monitors free space in the database log files after considering the available disk size. Note: You require System Administrator privileges on the database server to execute this checkpoint. | 4.2:65 | 0x063300bc | Percent |
aag_cluster_members_state | Monitors the state of the nodes of all AlwaysOn availability groups of WSFC. Each number is assigned a value, as follows:
| 4.2.3:2 | 0x063300bd | State |
aag_cluster_quorum_state | Monitors the quorum state of all AlwaysOn availability groups of Windows Server Failover Clustering (WSFC) cluster. Each number is assigned a value, as follows:
| 4.2.3:1 | 0x063300be | State |
aag_db_page_status | Monitors the page state of each database in all the AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:9 | 0x063300bf | State |
aag_db_replica_synchronization_state | Monitors the synchronization state of each database replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:8 | 0x063300c0 | State |
aag_listener_state | Monitors the listener state of all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:10 | 0x063300c1 | State |
aag_replica_connected_state | Monitors the connected state of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:5 | 0x063300c2 | State |
aag_replica_operational_state | Monitors the operational state of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:7 | 0x063300c3 | State |
aag_replica_recovery_health | Monitors the recovery health of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:6 | 0x063300c4 | State |
aag_replica_synchronization_health | Monitors the synchronization health of a replica in all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:4 | 0x063300c5 | State |
aag_synchronization_health | Monitors the synchronization health of all AlwaysOn availability groups of the server. Each number is assigned a value, as follows:
| 4.2.3:3 | 0x063300c6 | State |
wait_stats_count | Monitors the count of all the wait checkpoints, and displays the delta value of two intervals in the QoS. For example, if the current interval value is 20, and the previous interval value is 15, the delta value displayed is 5 (20-5). The alarm is generated if the delta value breaches the defined threshold. | 4.2:71 | 0x063300c7 | Count |
wait_stats_time | Monitors the total wait time in milliseconds for each wait checkpoint, and displays the delta value of two intervals in the QoS. For example, if the current interval value is 30 seconds, and the previous interval value is 20 seconds, the delta value displayed is 10 seconds (30-20). The alarm is generated if the delta value breaches the defined threshold. | 4.2:72 | 0x063300c8 | Milliseconds |
The CPU, Disk, Memory Performance Monitoring (cdm) probe monitors the performance and resource load on the system with the robot. The CA UIM CPU, Disk & Memory (cdm) probe generates alarms that are based on configured threshold values and trending statistics.
Metric Name | Description | Metric Type | CA Spectrum Event ID | Units |
system_uptime | Details how long the system has been on since its last restart. | 1:1 | 0x063300c9 | Seconds |
system_reboot | 1:2 | 0x063300ca | ||
system_disk_usage_mb | Aggregated disk usage in megabytes | 1.1:2 | 0x063300cb | Megabytes |
system_disk_usage_pct | Aggregated disk usage in percentage | 1.1:3 | 0x063300cc | Percent |
system_inode_usage_cnt | Total number of free file nodes in file system | 1.1:4 | 0x063300cd | Count |
system_inode_usage_pct | Total number of free file nodes in file system in percentage. | 1.1:5 | 0x063300ce | Percent |
system_shared_folder_availability | Populates the data depending upon the disk availability.
The available options are: Missing, New and Ok. | 1.1:7 | 0x063300cf | State |
system_disk_usage_delta | Disk Usage Delta Error
Warning Threshold - 8, Error Threshold - 200 | 1.1:8 | 0x063300d0 | |
system_disk_size_gb | Total size of the disk | 1.1:9 | 0x063300d1 | Gigabytes |
system_read_throughput | Disk bytes read per second | 1.1:58 | 0x063300d2 | Bytes/Second |
system_write_throughput | Disk bytes written per second | 1.1:59 | 0x063300d3 | Bytes/Second |
system_total_throughput | Disk bytes read and written per second | 1.1:60 | 0x063300d4 | Bytes/Second |
system_disk_partition_used_pct | Aggregated disk usage in percentage | 1.1.2:2 | 0x063300d5 | Percent |
system_disk_partition_used_mbytes | Aggregated disk usage in megabytes | 1.1.2:11 | 0x063300d6 | Megabytes |
system_user_cpu | The sum of CPU time when all CPUs of the system were executing the kernel or operating system | 1.5:1 | 0x063300d7 | Percent |
system_user_cpu_pct | The percentage of time for which all CPUs of the system were used. | 1.5:2 | 0x063300d8 | Percent |
system_system_cpu_pct | The CPU Usage Percentage detailis | 1.5:3 | 0x063300d9 | Percent |
system_wait_cpu_pct | The percentage of time for which all CPUs of the system were waiting for I/O. | 1.5:4 | 0x063300da | Percent |
system_idle_cpu_pct | The percentage of time for which all CPUs of the system were idle. | 1.5:5 | 0x063300db | Percent |
system_multi_cpu_usage_diff_pct | Multi-CPU Usage Difference in percentage | 1.5:6 | 0x063300dc | Percent |
system_multi_cpu_usage_pct | The percentage of time for which an individual CPU of the system was used. | 1.5:7 | 0x063300dd | Percent |
system_data_collection | System data collection | 1.5:8 | 0x063300de | |
system_processor_queue_length | The current calculated average load of the system. | 1.5:9 | 0x063300df | Processes |
system_load_avg_1min | The average system load over the last one minute. Note: This metric is supported only on the Linux, AIX and HP-UX platforms. | 1.5:68 | 0x063300e0 | Count |
system_load_avg_5min | The average system load over the last five minutes. Note: This metric is supported only on the Linux, AIX and HP-UX platforms. | 1.5:69 | 0x063300e1 | Count |
system_load_avg_15min | The average system load over the last fifteen minutes. Note: This metric is supported only on the Linux, AIX and HP-UX platforms | 1.5:70 | 0x063300e2 | Count |
system_multi_cpu_system_pct | Multi-CPU System Usage in percentage | 1.5.1:3 | 0x063300e3 | Percent |
system_multi_cpu_idle_pct | Multi-CPU System Idle in percentage | 1.5.1:5 | 0x063300e4 | Percent |
system_memory_usage_mb | Total memory usage in megabytes | 1.6:1 | 0x063300e5 | Megabytes |
system_memory_usage_pct | Total memory usage in percentage | 1.6:2 | 0x063300e6 | Percent |
system_memory_data_collection | System memory usage in percentage | 1.6:3 | 0x063300e7 | Percent |
system_system_memory_usage_pct | Total System memory utilization in percent. This metric is supported only on the Windows, Linux and AIX platforms. | 1.6:57 | 0x063300e8 | Percent |
system_user_memory_usage_pct | Total User memory utilization in percent. This metric is supported only on the Windows, Linux and AIX platforms. | 1.6:58 | 0x063300e9 | Percent |
system_physical_memory_usage_mb | The size of the physical memory used on the system in megabytes.
Note: For this metric, the buffer cache will be subtracted from physical memory value if the key mem_buffer_used is set as No . This support is added for Linux, AIX, and HPUX platforms. | 1.6:6 | 0x063300ea | Megabytes |
system_physical_memory_usage_pct | Total Swap memory usage in percent | 1.6:7 | 0x063300eb | Percent |
system_swap_memory_usage_mb | Total Swap memory usage in megabytes | 1.6:8 | 0x063300ec | Megabytes |
system_inbound_traffic | The total number of bytes per second received by the server. | 2.1.1:1 | 0x063300ed | Bytes/Second |
system_outbound_traffic | The total number of bytes per second sent by the server. | 2.1.1:2 | 0x063300ee | Bytes/Second |
system_aggregated_traffic | The total number of bytes per second sent and received by the server. | 2.1.1:3 | 0x063300ef | Bytes/Second |
net_connect (Network Connectivity Monitoring) probe measures network connectivity that is based on "ping" (ICMP ECHO) and the TCP connections to a list of user-defined services. The service can be NetBIOS, Telnet, FTP, and HTTP. The probe supports the CA UIM family of solutions by sending quality of service (QoS) messages.
Metric Name | Description | Metric Type | CA Spectrum Event ID | Units |
net_connect_misc | 2.2:1 | 0x063300f0 | ||
net_connect_response_time | Response time for network connectivity. | 2.2.1:1 | 0x063300f1 | Milliseconds |
net_connect_packet_loss | Percentage of Packet Loss in network connectivity response. Packet Loss Jitter and Latency QoS Calculation in net_connect Metrics. | 2.2.1:2 | 0x063300f2 | Milliseconds |
net_connect_nw_connectivity_response_pkt | Delay in time it takes a packet to cross a network. Latency = Jitter and Latency QoS Calculation. | 2.2.1:3 | 0x063300f3 | |
net_connect_nw_conn_response_packet_loss_jitter | Variable Latency in a network. Jitter = Jitter and Latency QoS Calculation in net_connect Metrics. | 2.2.1:4 | 0x063300f4 | Milliseconds |
net_connect_tcp_response_time | Response time for network connectivity. | 2.2.2:1 | 0x063300f5 | Milliseconds |
The (Process Monitoring) processes probe monitors the specified processes to detect any error situation. The probe also retrieves information about the process, for example, the CPU usage, memory usage, and so on.
Metric Name | Description | Metric Type | CA Spectrum Event ID | Units |
ipc_number_processes_cnt | The number of Instances of a process | 1.26:1 | 0x063300f6 | Count |
ipc_processes_util | The percentage of number of processes currently running in the system to maximum number of processes configured in the system | 1.26:2 | 0x063300f7 | Percent |
ipc_number_semaphore_sets | The number of semaphore sets currently used by the system | 1.26:3 | 0x063300f8 | Number |
ipc_number_semaphore_sets_util | The percentage of Semaphore Sets currently used by the System to maximum number of semaphore sets configured in the system | 1.26:4 | 0x063300f9 | Percent |
ipc_message_queue_cnt | The number of message queues currently used by the system | 1.26:5 | 0x063300fa | Count |
ipc_message_queue_util | The percentage of message queues currently used by system to maximum number of message queues configured in the system | 1.26:6 | 0x063300fb | Percent |
ipc_number_shared_mem_segments | The number of Shared Memory Segments currently used by the system | 1.26:7 | 0x063300fc | Count |
ipc_number_shared_mem_seg_util | The percentage of Shared Memory Segments currently used by the System to maximum number of shared memory segments configured in the system. | 1.26:8 | 0x063300fd | Count |
processes_instances | The number of processes currently running in system | 1.3:2 | 0x063300fe | Number |
processes_state | The availability (up/down) of a process | 1.3:3 | 0x063300ff | State (Up/Down) |
processes_mem_usage | The bytes of memory utilized by a process | 1.3:4 | 0x06330100 | Bytes |
processes_cpu_usage | The percentage of CPU utilization by a process | 1.3:5 | 0x06330101 | Percent |
processes_threads | The number of threads of a process | 1.3:6 | 0x06330102 | Count |
processes_unexpected_user | Process not running with expected user | 1.3:22 | 0x06330103 | Count |
processes_handles_cnt | The number of handles of a process | 1.3:42 | 0x06330104 | Count |
processes_resident_mem_usage | Process exceeds the expected resident memory usage
Note: This metric is only supported on Linux. | 1.3:45 | 0x06330105 | Kilobytes |
The Log Monitoring (logmon) probe scans ASCII-based systems and application log files by matching specified expressions. Alarms are generated when the log file content matches the defined expression. The probe also extracts and stores metric data from the matched log file entry in the QoS database.
Metric Name | Description | Metric Type | CA Spectrum Event ID |
logmon_exit_code (only for Command profile) | Exit code threshold breach/ clear | 1.2.3:4 | 0x06330106 |
logmon_url_response_probe_state (only for URL profile) | Contact Success (Clear) / Contact Failed | 1.2.4:4 | 0x06330107 |
logmon_url_load_state | URL load success (Clear)/ Failed. | 1.2.4:5 | 0x06330108 |
logmon_misc | 1.2.5:4 | 0x06330109 |
The Remote System Probe (rsp) allows you to monitor system metrics. The probe collects performance data in an agent-less manner without installing proprietary software on the system.
Metric Name | Description | Metric Type | CA Spectrum Event ID | Units |
rsp_processes_owner | Alarm to be issued when the configured threshold is satisfied | 1.3:1 | 0x0633010a | |
rsp_processes_instances | Number of process instances. | 1.3:2 | 0x0633010b | Number |
rsp_processes_state | Process availability. | 1.3:3 | 0x0633010c | State |
rsp_processes_memory_usage | Process memory usage. | 1.3:4 | 0x0633010d | Kilobytes |
rsp_processes_cpu_usage | Process CPU usage. | 1.3:5 | 0x0633010e | Percent |
rsp_processes_threads | Number of process threads. | 1.3:6 | 0x0633010f | Number |
rsp_service_state | Network Service Availability | 1.4:1 | 0x06330119 | State |
rsp_processor_queue_length | Processor queue length. The current calculated average load of the system. | 1:3 | 0x06330116 | Processes |
rsp_multi_cpu_usage_pct | Difference between highest and lowest CPU usage on Multi-CPU systems. The metric calculates data in percentage for the individual CPU idle time, user time, system time, wait time, and CPU usage. | 1.5.1:1 | 0x06330117 | Percent |
rsp_cpu_usage_pct | CPU usage. The metric calculates data in percentage for total usage, user time, system time, wait time, and idle time. | 1.5:1 | 0x06330118 | Percent |
rsp_mem_usage_pct | Total memory usage in percent. | 1.6:2 | 0x06330114 | Percent |
rsp_mem_paging | Memory paging in kilobytes per second. | 1.6:4 | 0x06330115 | Kilobytes/Second |
rsp_number_events | Number of events in interval. This metric sends the count of matched events, irrespective of the profile. | 1.2.1:1 | 0x06330113 | Count |
rsp_disk_availability | 1.1:1 | 0x06330110 | ||
rsp_disk_usage_mb | Aggregated disk I/O rate in megabytes. | 1.1:2 | 0x06330111 | Megabytes |
rsp_disk_usage_pct | Aggregated disk I/O rate in percentage. | 1.1:3 | 0x06330112 | Percent |