vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Classic virtual server instance metrics definitions 

The following metrics are associated with the IBM Cloud Monitoring full agent. If you provisioned a 'no driver mode' instance, see [IBM Cloud Monitoring 'no driver mode' metrics](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-enabling-monitoring-light-no-driversysdig-light-metrics).

The following tables define basic Classic virtual server instance metrics.



 Average CPU usage percentage 

Average percentage of time that elapsed running instructions across all CPUs



Table 1: Average CPU usage percentage metric metadata

 Metadata Description 

 Metric name ibm_is_instance_average_cpu_usage_percentage 
 Metric type gauge 
 Value type percent 
 Segment by IBM IS Generation, 1, resource name 







 CPU usage 

Cumulative elapsed time that a CPU is running instructions since virtual server instance start



Table 2: Cumulative CPU usage metric metadata

 Metadata Description 

 Metric name ibm_is_instance_cpu_usage_nanoseconds 
 Metric type gauge 
 Value type second 
 Segment by IBM IS Generation, 1, resource name, Virtual CPU index 







 CPU usage percentage 

Average percentage of time that a CPU is running instructions



Table 3: Average CPU usage metric metadata

 Metadata Description 

 Metric name ibm_is_instance_cpu_usage_percentage 
 Metric type gauge 
 Value type percent 
 Segment by IBM IS Generation, 1, resource name, Virtual CPU index 







 Free memory 

Free memory of the virtual server instance in kibibytes (1024 bytes)



Table 4: Free memory metric metadata

 Metadata Description 

 Metric name ibm_is_instance_memory_free_kib 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation, 1, resource name 







 I/O requests in flight 

Number of I/O requests in flight



Table 5: I/O requests in flight metric metadata

 Metadata Description 

 Metric name ibm_is_instance_volume_in_flight 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation, 1, resource name, disk name of the volume, UUID of storage volume 







 Memory usage percentage 

Percent of used memory of the virtual server instance
Table 7: VPN server metric attributes

 Attribute Attribute name Attribute description 

 Cloud type ibm_ctype A value of public, dedicated, or local. 
 Location ibm_location The location of the monitored resource - a region, data center, or global. 
 Resource ibm_resource The resource that is measured by the service - typically an identifying name or GUID. 
 Resource type ibm_resource_type The type of resource that is measured by the service. 
 Resource group ibm_resource_group_name The resource group where the service instance was created. 
 Scope ibm_scope The scope of the account, organization, or space GUID that is associated with this metric. 
 Service name ibm_service_name The name of the service that generated this metric. 







 Additional attributes 

The following attributes are available for segmenting one or more attributes as described in the previous reference. See the individual metrics for segmentation options.



Table 8: VPN server segmentation metric attributes

 Attribute Attribute name Attribute description 

 Service instance ibm_service_instance Identifies the instance that the metric is associated with. 
 Service instance name ibm_service_instance_name Provides the user provided name of the service instance. This name isn't necessarily a unique value that depends on the name that is provided. 
 VPN server name ibm_is_vpn_server_name The IBM VPN for VPC server name. 



The displayed metrics contain a timestamp in UNIX epoch time and the metric value for the time intervals that end at that timestamp. You can specify different scopes, and the time interval over which to report the metrics.

The following time intervals are supported in the IBM Cloud Monitoring dashboard:



* 10 seconds
* 1 minute
* 10 minutes
* 1 hour
* 6 hours
* 2 weeks
* Custom









 Enabling metrics monitoring 

To receive monitoring metrics, you must set up your IBM Cloud Monitoring instance.

To receive monitoring metrics, use the following steps:



1. Navigate to the [metrics monitoring portal](https://cloud.ibm.com/observe/monitoring) and click Create a monitoring instance.
2. Select a region for your IBM Cloud Monitoring instance.
Metric Name ibm_metrics_router_successful_data_points 
 Metric Type gauge 
 Value Type none 
 Segment By ibm_ctype,ibm_location, ibm_scope, ibm_service_name, ibm_resource_type, ibm_resource_name, ibm_resource, ibm_metrics_router_target_type 
 Frequency 60 seconds 







 The current target mode 

The current mode for IBM Cloud Metrics Routing targets. There are two possible values for the metric:



* 1 is for valid targets.
* 0 is for misconfigured targets.



It is your responsibility to resolve misconfigured targets, at least one of the following needs to be fixed:



1. You must have the correct service-to-service authorizations, see [Managing authorizations to grant access between services](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-iam-service-auth&interface=ui).
2. Your target destination must be a CRN for a Cloud instance that still exists.





Table 2. The current target mode

 Metadata Description 

 Metric Name ibm_metrics_router_target_mode 
 Metric Type gauge 
 Value Type none 
 Segment By ibm_ctype,ibm_location, ibm_scope, ibm_service_name, ibm_resource_type, ibm_resource_name, ibm_resource, ibm_metrics_router_target_type 
 Frequency 60 seconds 







 Global Attributes 

The following attributes are available for all metrics.



Table 3. Global attributes

 Attribute Attribute Name Attribute Description Valid values 

 Cloud Type ibm_ctype The cloud type can be public, dedicated, or local. Valid value is public. 
 Location ibm_location The location of the monitored resource, which can be a region, data center, or global. [Valid regions](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions). 
 Resource ibm_resource The resource that is measured by the service, which is typically an identifying name or GUID.
Metadata Description 

 Metric Name ibm_mq_qmgr_mqstat_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 







 MQSUBRQ count 

Total MQSUBRQ count for a queue manager



Table 38: MQSUBRQ count metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_mqsubrq_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 







 Non-persistent - topic MQPUT/MQPUT1 count 

Total non-persistent topic MQPUT/MQPUT1 count for a queue manager



Table 39: Non-persistent - topic MQPUT/MQPUT1 count metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_non_persistent_topic_mqput_mqput1_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 







 Non-persistent message MQPUT count 

Total non-persistent message MQPUT count for a queue manager



Table 40: Non-persistent message MQPUT count metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_non_persistent_message_mqput_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 







 Non-persistent message MQPUT1 count 

Total non-persistent message MQPUT1 count for a queue manager



Table 41: Non-persistent message MQPUT1 count metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_non_persistent_message_mqput1_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 







 Non-persistent message browse - byte count 

Total non-persistent message browse byte count for a queue manager



Table 42: Non-persistent message browse - byte count metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_non_persistent_message_browse_bytes_total 
 Metric Type counter 
 Value Type byte 
 Segment By Service instance, The queue manager name
[View metrics by storage class](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/SysDig-COS-metrics-3.jpg)

Figure 5. View used space by storage class







 Cloud Object Storage metrics details 



 Usage metrics 

There are a set of basic metrics that track usage:



* ibm_cos_bucket_used_bytes
* ibm_cos_bucket_object_count
* ibm_cos_bucket_hard_quota_bytes







 Request metrics 

There are metrics that report the aggregates for different classes of HTTP requests:



* ibm_cos_bucket_all_requests
* ibm_cos_bucket_get_requests
* ibm_cos_bucket_put_requests
* ibm_cos_bucket_delete_requests
* ibm_cos_bucket_post_requests
* ibm_cos_bucket_list_requests
* ibm_cos_bucket_head_requests



Errors are also collected, with server-side (5xx) errors broken out:



* ibm_cos_bucket_4xx_errors
* ibm_cos_bucket_5xx_errors



The minimum, maximum, and average bytes transferred by network type are reported:



* ibm_cos_bucket_bytes_download_public_min
* ibm_cos_bucket_bytes_download_public_max
* ibm_cos_bucket_bytes_download_public_avg
* ibm_cos_bucket_bytes_download_private_min
* ibm_cos_bucket_bytes_download_private_max
* ibm_cos_bucket_bytes_download_private_avg
* ibm_cos_bucket_bytes_download_direct_min
* ibm_cos_bucket_bytes_download_direct_max
* ibm_cos_bucket_bytes_download_direct_avg
The metric ipmi_scrape_duration_seconds reports the amount of time that it takes the collector to retrieve the data.
* IPMI System event log (SEL) metrics

The metric ipmi_sel_entries_count reports the number of entries in the system event log.

The metric ipmi_sel_free_space_bytes reports the number of free bytes for new ystem event log entries.
* IPMI sensor data

The IPMI exporter collects 2 metrics per sensor type: state and value. A value of 0 reports a normal state. A value of 1 reports a warning state. A value of 2 reports a critical state. A value of NaN reports information not available. For example, see the metrics for different sensors:

Temperature sensor metrics: ipmi_temperature_celsius, ipmi_temperature_state

Fan speed sensor metrics: ipmi_fan_speed_rpm, ipmi_fan_speed_state

Voltage sensor metrics: ipmi_voltage_state, ipmi_voltage_volts
* IPMI chassis power state of the machine

The metric ipmi_chassis_power_state informs about the current state of the chassis of the machine. It has a value of 1 when the power is on. It has a value of 0 when the power is off.
* DCMI data

The metric ipmi_dcmi_power_consumption_current_watts informs about the live power consumption of the machine in Watts.
* BMC details

The metric ipmi_bmc_info includes information about the firmware revision and manufacturer in labels and has a value of 1.



For more information, see [Prometheus IPMI Exporter](https://github.com/soundcloud/ipmi_exporter).

Complete the following steps to configure a monitoring agent to collect IPMI metrics from 1 or more hosts:



 Step 1: Configure a monitoring agent 

To monitor 1 or more hosts, you must configure a monitoring agent. The agent collects automatically a set of metrics that you can monitor through the monitoring UI.
The automatic collection of IBM Cloud Metrics Routing metrics in Americas locations

 Locations in Americas Service metrics available 

 Dallas (us-south) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/icons/checkmark-icon.svg) 
 Washington DC (us-east) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/icons/checkmark-icon.svg) 





Table 3. The automatic collection of IBM Cloud Metrics Routing metrics in Asia Pacific locations

 Locations in Asia Pacific Service metrics available 

 Sydney (au-syd) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/icons/checkmark-icon.svg) 





Table 4. The automatic collection of IBM Cloud Metrics Routing metrics in Europe locations

 Locations in Europe Service metrics available 

 Frankfurt (eu-de) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/icons/checkmark-icon.svg) 
 London (eu-gb) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/icons/checkmark-icon.svg) 







 Monitoring IBM Cloud Metrics Routing 

You monitor the health and status of IBM Cloud Metrics Routing by monitoring metrics through the Monitoring web UI.
The following attributes are available for segmenting all of the metrics listed above



 Attribute Attribute Name Attribute Description 

 Cloud Type ibm_ctype The cloud type is a value of public, dedicated or local 
 Location ibm_location The location of the monitored resource - this may be a region, data center or global 
 Resource ibm_resource The database member resource being measured by the service 
 Scope ibm_scope The scope is the account, organization or space GUID associated with this metric 
 Service name ibm_service_name Name of the service generating this metric 







 Additional Attributes 

The following attributes are available for segmenting one or more attributes as described in the reference above. Please see the individual metrics for segmentation options.



 Attribute Attribute Name Attribute Description 

 Service instance ibm_service_instance The service instance segment identifies the instance the metric is associated with
* [IBM Cloud Schematics metrics details](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instancesmetrics-details)



* [ibm_schematics_workspace_count](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instanceswkspace-count)
* [ibm_schematics_workspace_actions_count](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instanceswkspace-actions-count)
* [ibm_schematics_vulnerability_count](https://cloud.ibm.com/docs/schematics?topic=schematics-monitoring-instanceswkspace-vulnerability-count)





[Auditing events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsat_events)



* [Schematics events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsschematics-events)



* [Workspace events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsschematics-wks-events)
* [Action events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsschematics-action-events)
* [Job events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsschematics-job-events)
* [Shareddata events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsschematics-shareddata-events)
* [Other events](https://cloud.ibm.com/docs/schematics?topic=schematics-at_eventsschematics-otherevents)
Table 61: Topic MQPUT/MQPUT1 interval total metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_topic_mqput_mqput1_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 









 Attributes for Segmentation 



 Global Attributes 

The following attributes are available for segmenting all of the metrics listed above



 Attribute Attribute Name Attribute Description 

 Cloud Type ibm_ctype The cloud type is a value of public, dedicated or local 
 Location ibm_location The location of the monitored resource - this may be a region, data center or global 
 Resource ibm_resource The resource being measured by the service - typically a indentifying name or GUID 
 Resource Type ibm_resource_type The type of the resource being measured by the service 
 Resource group ibm_resource_group_name The resource group where the service instance was created 
 Scope ibm_scope The scope is the account, organization or space GUID associated with this metric 
 Service name ibm_service_name Name of the service generating this metric 







 Additional Attributes 

The following attributes are available for segmenting one or more attributes as described in the reference above. Please see the individual metrics for segmentation options.



 Attribute Attribute Name Attribute Description 

 Service instance ibm_service_instance The service instance segment identifies the instance the metric is associated with 
 The queue manager name ibm_mq_qmgr_name The queue manager name
Table 23: Transaction commit rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_transaction_commit_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Transaction rollback count 

Transaction rollback count



Table 24: Transaction rollback count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_transaction_rollback_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Transaction rollback rate 

Transaction rollback rate



Table 25: Transaction rollback rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_transaction_rollback_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Tuples deleted count 

Tuples deleted count



Table 26: Tuples deleted count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_tuples_deleted_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Tuples deleted rate 

Tuples deleted rate



Table 27: Tuples deleted rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_tuples_deleted_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Tuples fetched count 

Tuples fetched count



Table 28: Tuples fetched count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_tuples_fetched_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance 







 Tuples fetched rate 

Tuples fetched rate



Table 29: Tuples fetched rate metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_tuples_fetched_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Tuples inserted count 

Tuples inserted count



Table 30: Tuples inserted count metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_postgresql_tuples_inserted_count 
 Metric Type gauge 
 Value Type none
The metric ipmi_scrape_duration_seconds reports the amount of time that it takes the collector to retrieve the data.
* IPMI System event log (SEL) metrics

The metric ipmi_sel_entries_count reports the number of entries in the system event log.

The metric ipmi_sel_free_space_bytes reports the number of free bytes for new ystem event log entries.
* IPMI sensor data

The IPMI exporter collects 2 metrics per sensor type: state and value. A value of 0 reports a normal state. A value of 1 reports a warning state. A value of 2 reports a critical state. A value of NaN reports information not available. For example, see the metrics for different sensors:

Temperature sensor metrics: ipmi_temperature_celsius, ipmi_temperature_state

Fan speed sensor metrics: ipmi_fan_speed_rpm, ipmi_fan_speed_state

Voltage sensor metrics: ipmi_voltage_state, ipmi_voltage_volts
* IPMI chassis power state of the machine

The metric ipmi_chassis_power_state informs about the current state of the chassis of the machine. It has a value of 1 when the power is on. It has a value of 0 when the power is off.
* DCMI data

The metric ipmi_dcmi_power_consumption_current_watts informs about the live power consumption of the machine in Watts.
* BMC details

The metric ipmi_bmc_info includes information about the firmware revision and manufacturer in labels and has a value of 1.



For more information, see [Prometheus IPMI Exporter](https://github.com/soundcloud/ipmi_exporter).

Complete the following steps to configure the Prometheus IPMI Exporter:



 Install the Prometheus IPMI exporter 

Complete the following steps:



1. From a local terminal, [download the Prometheus IPMI exporter](https://github.com/soundcloud/ipmi_exporter).
2.
* Resource usage metrics: Resource usage metrics reports on the health and state of CPU and memory for workers (nodes) and pods that are running in the cluster. The data can be analyzed by namespace, by worker, by pod, by workload object such as deployments, daemonSets, and more.



For a list of collected metrics, see [Metrics Available for orchestrated environments](https://docs.sysdig.com/en/docs/sysdig-monitor/using-monitor/metrics/metrics-library/prometheus-format/).

Through the Monitoring UI, you can analyze data in the Advisor tab, the Explore tab, and in the Dashboard tab. You monitor the data through metric views and dashboards.

Consider the following information when monitoring your data:



* In the Explorer tab, you can monitor individual metrics.
* In the Advisor tab, you can monitor Kubernetes or host level metrics.

This tab is only available for users that belong to a team that has access to monitor Kubernetes or host level metrics.
* In the Dashboard tab, you can monitor through panels predefined dashboards or custom ones and get a specialized insight into network data, application data, topology, services, hosts, and containers. A panel displays a metric or group of metrics in a dashboard.



For each metric view and dashboard, you can define the scope of the data, how to aggregate data, and what time and group filters to apply to the data. For more information, see [Managing panels](https://cloud.ibm.com/docs/monitoring?topic=monitoring-panels).

You can configure a dashboard as the default entry point for a team, unifying a team's experience, and allowing users to focus their immediate attention on the most relevant information for them.

For more information, see [Viewing metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-monitoring).



 Objectives 

In this tutorial, you configure metrics for your IBM Cloud® Kubernetes Service cluster. In particular, you:



* Provision an IBM Cloud Monitoring instance.
[0] => SoftLayer_Container_Network_CdnMarketplace_Metrics: {
type: 'REALTIME',
names: [
'TotalHits',
'TotalBandwidth'
],
totals: [
1301, Total hits from the start time to the end time
20.05 Total bandwidth from the start time to the end time
],
time: [
1576627200,
1576630800,
1576634400,
1576638000,
1576641600,
1576645200,
1576648800,
1576652400,
1576656000,
1576659600,
1576663200
],
yaxis1: [ Hits divided with the given time interval
123,
23,
345,
12,
33,
78,
89,
87,
234,
12,
43
],
yaxis2: [ Bandwidth divided with the given time interval
1.21,
2.32,
0.45,
1.03,
3.01,
2.55,
4.98,
2.45,
10.23,
2.12,
8.97
]
}
)
Show more

To get the real-time metrics for a domain mapping, you can call the getMappingRealTimeMetrics API.

$client = SoftLayerSoapClient::getClient('SoftLayer_Network_CdnMarketplace_Metrics', null, $apiUsername, $apiKey);
try {
$metrics = $client->getMappingRealTimeMetrics(
123456789123456, // Mapping unique id
1576627200, // Start timestamp, must be later than 48 hours ago
1576663200, // End timestamp, must be later than start time
* [Event severity](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-at-eventsuko-event-severity)







 Logging and monitoring 

[Managing metrics](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-monitoring-metricsmanage-monitoring-metrics)



* [Managing metrics settings](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-monitoring-metricsmanage-metrics-policy)
* [What's next](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-monitoring-metricsmonitor-metrics-next-steps)



[Monitoring operational metrics](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsoperational-metrics)



* [What metrics are available for Hyper Protect Crypto Services?](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricshpcs-metrics-available)
* [Before you begin](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsoperational-metrics-considerations)
* [Connecting Monitoring with Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsconnect-monitoring-hpcs)
* [Hyper Protect Crypto Services Metrics Details](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricshpcs-metrics)
* [Latency](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricslatency)