vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Metric Name ibm_mq_qmgr_failed_mqget_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, The queue manager name 







 Failed MQINQ count 

Total number of failed MQINQ for a queue manager



Table 13: Failed MQINQ count metric metadata

 Metadata Description 

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







 Failed MQOPEN count 

Total number of failed MQOPEN for a queue manager



Table 14: Failed MQOPEN count metric metadata

 Metadata Description 

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







 Failed MQPUT count 

Total number of failed MQPUT for a queue manager



Table 15: Failed MQPUT count metric metadata

 Metadata Description 

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







 Failed MQPUT1 count 

Total number of failed MQPUT1 for a queue manager



Table 16: Failed MQPUT1 count metric metadata

 Metadata Description 

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







 Failed MQSET count 

Total number of failed MQSET for a queue manager



Table 17: Failed MQSET count metric metadata

 Metadata Description 

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







 Failed MQSUBRQ count 

Total number of failed MQSUBRQ for a queue manager



Table 18: Failed MQSUBRQ count metric metadata

 Metadata Description 

 Metric Name ibm_mq_qmgr_failed_mqsubrq_total 
 Metric Type counter 
 Value Type none
[Query](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/query.png)

You can see a metric that is collected by using the Prometheus remote write feature.

![Metric](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/metric.png)
6. Click Save to create the panel that monitors the metric in the dashboard.







 Known issues 



 Prom-Beacon service not enabled 

If you find the following log entry in the logs of the Prometheus server that is deployed in your cluster, your Monitoring instance does not have the Prom-Beacon service enabled.

ts=2021-05-05T13:32:16.975Z caller=dedupe.go:112 component=remote level=warn remote_name=2e147e url=https://ingest.us-south.monitoring.cloud.ibm.com/prometheus/remote/write msg="Failed to send batch, retrying" err="server returned HTTP status 503 Service Unavailable: {"errors":[{"reason":"Customer settings error","message":"Prom-Beacon service not enabled"}]}"

To solve the problem, open a support ticket. You can [create](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case) and [manage](https://cloud.ibm.com/docs/get-support?topic=get-support-managing-support-cases) a support case by using the [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).
:3],"sequence":{"ch":"d3","label":"X90p_d3","name":"parametric_pulse","parameters":{"amp":0.0874162373846442,0.0021564674084263613],"beta":-2.147473654798121,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0}]},{"name":"sx","qubits":4],"sequence":{"ch":"d4","label":"X90p_d4","name":"parametric_pulse","parameters":{"amp":0.09398545949749511,0.0010006507509606616],"beta":-0.8252889412167893,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0}]},{"name":"sx","qubits":5],"sequence":{"ch":"d5","label":"X90p_d5","name":"parametric_pulse","parameters":{"amp":0.093893323098105,0.0018717804654582596],"beta":-0.10948062656433855,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0}]},{"name":"sx","qubits":6],"sequence":{"
If you want to see this metric for all of your VPN gateways, do not enter a value for the scope attribute. For example, use "scope" : "".



* The metric type that you want to see the results for. This example uses ibm_is_vpn_gateway_status.
* The from and to attributes define the timeframe to focus the scan, set in epoch time, and in microseconds.
* The sampling and value attributes set the granularity of the data that is returned in the POST request.



Because a large volume of data is stored in IBM Cloud Monitoring, choosing the specific level of granularity is important. IBM Cloud Monitoring can return only 600 data points at a time per request. As a result, the sampling and value attributes are important. Leaving these two lines out of your request returns an aggregate sum over that time period instead.

If the time range that is specified by from and to is large (for example, 4 days), but you define a sampling and value of 10 seconds, it means that you receive 4 days worth of data that is split into 10-second chunks. This sample is not useful because of the large amount of data that is returned. Specifying a larger chunk is recommended (for example, 1 hour instead of 10 seconds).

curl -H 'Authorization: Bearer <API_TOKEN>’ -H 'Content-Type: application/json' https://us-south.monitoring.cloud.ibm.com/api/data/batch -d '{
"requests": [
{
"format": {
"type": "data"
},
"scope": "ibm_is_vpn_gateway_name = "test-001"",
"metrics": {
"k0": "timestamp",
"v1": "ibm_is_vpn_gateway_status"
},
"time": {
"from": 1589877054000000,
"to": 1589877114000000,
"sampling": 60000000
},
"group": {
"by":
$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
60 // Time interval, must be a multiple of 60 seconds
);
print_r($vendors);
} catch (Exception $e) {
die('Unable to get mapping real-time metrics: ' . $e->getMessage());
}

The getMappingRealTimeMetrics API returns an array of metrics. Example output is as follows:

(
[0] => SoftLayer_Container_Network_CdnMarketplace_Metrics: {
type: 'REALTIME',
names: [
'TotalHits',
'TotalBandwidth',
'200',
'206',
'2XX',
'302',
'304',
'3XX',
'401',
'403',
'404',
'412',
'4XX',
'5XX',
'Error',
'Others'
],
totals: [
1301, Total hits from the start time to the end time
20.05, Total bandwidth from the start time to the end time
100, Total Hits with hits type 200
200, Total Hits with hits type 206
200, Total Hits with hits type 2XX
300, Total Hits with hits type 302
100, Total Hits with hits type 304
200, Total Hits with hits type 3XX
300, Total Hits with hits type 401
100, Total Hits with hits type 403
200, Total Hits with hits type 404
Ten main metrics in the dashboard are shown. These metrics include Gateway/Connection status, Gateway/Connection bytes input/output, and Gateway/Connection packets input/output. If you want to modify parameters and segment your metrics by VPN gateway name and VPN connection name, you must create a custom dashboard.

You can choose what time window that you'd like to see your metrics by using the time selection bar.







 Creating a custom metrics dashboard 

You can create your own dashboard to customize your monitoring metrics, such as viewing information about particular VPN gateways, or seeing traffic that comes through only a VPN connection.

To customize your dashboard, use the following steps:



1. Navigate to the [metrics monitoring portal](https://cloud.ibm.com/observe/monitoring).
2. Click Open dashboard next to the service name of the IBM Cloud Monitoring instance you want to work with. You now see the dashboard.
3. Select Dashboards and click the + in the panel.
4. Select Blank dashboard and select the type of visual representation that you want.

IBM Cloud Monitoring offers eight different visualizations for your dashboard. Read the description for each visualization and choose the one that best meets your requirements.

The line View trends over time is the most frequently selected option. The following examples show a line-based visualization.
5. Configure your custom dashboard.



* In the Metrics field, enter ibm_is to display the ten IBM Cloud VPN for VPC metrics: ibm_is_vpn_gateway_status, ibm_is_vpn_connection_status, ibm_is_vpn_gateway_bytes_in, ibm_is_vpn_gateway_bytes_out, ibm_is_vpn_gateway_packets_in, ibm_is_vpn_gateway_packets_out, ibm_is_vpn_connection_bytes_in, ibm_is_vpn_connection_bytes_out, ibm_is_vpn_connection_packets_in, and ibm_is_vpn_connection_packets_out.
* You can choose a scope to display in your dashboard by clicking Override Dashboard Scope.
Read a target GET <ENDPOINT>/api/v3/targets/<TARGET_ID> 
 List all targets GET <ENDPOINT>/api/v3/targets 



For more information, see [IBM Cloud Metrics Routing v3 API](https://cloud.ibm.com/apidocs/metrics-router).





 HTTP response codes 

When you use the IBM Cloud Metrics Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 6. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 204 OK The target was successfully deleted. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The authorization request fails. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Metrics Routing processing.
The dashboard would contain different lines showing 10 users who are connected through HTTP on Port 80 in one color, and 6 users connected through TCP on port 8080 in another color.



 Global attributes 

The following attributes are available for segmenting the three metrics.



Table 12: Global attributes

 Attribute Attribute Name Attribute Description 

 Resource ibm_resource A load balancer's unique ID 
 Scope ibm_scope The account that is associated with a given load balancer 
 Service name ibm_service_name ibm-is-load-balancer 







 Additional attributes 

The following attributes are available to segment one or more of the global attributes. See the individual metrics for any segmentation options.



Table 13: Additional attributes

 Attribute Attribute Name Attribute Description 

 Application load balancer appliance metrics ibm_is_load_balancer_appliance_ip The metrics coming from the load balancer back-end. Because the load balancer is highly available, multiple appliances support each load balancer for redundancy. 
 Application load balancer listener metrics ibm_is_load_balancer_listener_port The metrics that are gathered from individual listeners and their ports. Configure the listeners in your load balancer settings. The monitoring metrics reflect the metrics coming from those listeners. 
 Application load balancer pool metrics ibm_is_load_balancer_pool_name The metrics that are gathered from individual listener ports and the health check port (if a health check port is configured) or the back-end member ports (if a health check port is not configured). You must configure the listeners, back-end pool with members and, if needed, the health check port in your load balancer settings. The monitoring metrics reflect the metrics coming from those listeners and health check port, or the back-end member ports. 



The following sample values are for the ibm_is_load_balancer_pool_name attribute in its different configurations. If the pool has no members, then this value will be in the format Pool_ListenerPort. If the pool has members and the health check port is configured, then this value will be in the format Pool_ListenerPort:HealthCheckPort.
* [Script](https://cloud.ibm.com/docs/monitoring?topic=monitoring-agent_openshift)



The Monitoring agent automatically collects the following types of system metrics per host:



* System hosts metrics provide information about CPU, memory, and storage usage metrics, that you can use to analyze the performance and resource utilization of all your processes.
* File and File System metrics provide information about files and file system that you can use to analyze file interactions that occur in your system. For example, you can find information about your open files, bytes going in and out, or the percentage of usage of a given file system.
* Process metrics provide information about the processes that run in your servers. For example, you can use these metrics to explore the number of processes, or get client or server information.
* Network metrics provide information about the network. They offer insight to the connections that are established between your applications, containers, and servers. For example, you can find information about the bytes that are being sent or received, or the number of HTTP requests, connections, and latency. In addition, for SQL or MongoDB, the agent collects additional information when it is configured in troubleshooting mode.



The Monitoring agent automatically collects the following types of metrics per Red Hat OpenShift cluster:



* State metrics: Kube state metrics report on the health and state of the various objects that run inside Red Hat OpenShift components, such as deployments, nodes and pods. To see the list of metrics that are collected by default, see Red Hat OpenShift State.
* 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/).
For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).
3. Before you configure IBM Cloud Metrics Routing routes or targets, you must configure a primary metadata region. The primary metadata region is configured using the [modify settings API method.](https://cloud.ibm.com/apidocs/metrics-router/metrics-router-v3update-settings)







 Creating a Monitoring target using the API 

You can use the following cURL command to create a Monitoring target:

Target names are unique in the account.

curl -X POST <ENDPOINT>/api/v3/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json" -d '{
"name": "TARGET_NAME",
"destination_crn": "CRN"
}'

Where



* <ENDPOINT> is the API endpoint in the region where you plan to configure or manage a target. For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).
* TARGET_NAME is the name of the target. The maximum length of the name is 256 characters.

Do not include any personal identifying information (PII) in any resource names.
* CRN indicates the [CRN](https://cloud.ibm.com/docs/account?topic=account-crn) of the Monitoring instance.



For example, you can use the following cURL request to create a target in Dallas:

curl -X POST https://private.us-south.metrics-router.cloud.ibm.com/api/v3/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json" -d '{
"name": "My-target",
Managing panels 

Use a panel to display a metric or group of metrics in a dashboard. You can copy, change the scope, duplicate, delete, export, and explore panels.

You can use any of the following panel types:



Table 1. Panel types

 Type Description 

 Line Use this panel to view trends over time for one or more metrics. 
 Top list Use this panel to compare a metric across groups of entities. The bar chart is sorted in descending order. 
 Histogram Use this panel to view the frequency distribution of a metric in buckets. 
 Number Use this panel to view a single number that represents the value of an aggregated metric over time for one or more entities. 
 Table Use this panel to display numerical data for your infrastructure based on metrics and segments. 
 Text Use this panel to add text. Use markdown to add your text. 





 Copy a panel into a dashboard 

Complete the following steps to copy a panel:



1. Navigate to the Dashboards section (![dashboard section](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/monitor/images/dashboards.png)) in the Web UI. Select a dashboard. Then, identify the panel that displays the metric that you want to copy.
2. Click the Actions icon ![Three dots icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/monitor/images/actions.png) and select Copy to Dashboard![Copy to Dashboard icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/monitor/images/copy.png).
3. Select one of the dashboards that are listed, or enter a name for a new dashboard.
Metric Description The number of times agents have to wait for log data to write to disk. 







 Number of Unique ID statements 



Table 9. Number of unique ID statements metric

 Metadata Description 

 Metric Name ibm_db2_uid_stmts 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Resource 
 Metric Description The number of UPDATE, INSERT, MERGE and DELETE statements that were executed. 







 Number of rows deleted 



Table 10. Number of rows deleted metric

 Metadata Description 

 Metric Name ibm_db2_rows_deleted 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Resource 
 Metric Description Total of number of row deletions attempted and total number of rows deleted from the database as a result of internal activity. 







 Number of rows updated 



Table 11. Number of rows updated metric

 Metadata Description 

 Metric Name ibm_db2_rows_updated 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Resource 
 Metric Description Total number of row updates attempted and total number of rows updated from the database as a result of internal activity. 







 Numbers of rows inserted 



Table 12. Number of rows inserted metric

 Metadata Description 

 Metric Name ibm_db2_rows_inserted 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Resource 
 Metric Description Total number of row insertions attempted and total number of rows inserted from the database as a result of internal activity. 







 Time since last backup in hours 



Table 13. Time since last backup in hours metric

 Metadata Description 

 Metric Name ibm_db2_since_last_backup_hours 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance, Resource 
 Metric Description The number of hours since there was a last successful backup. 







 Total Activities Aborted 



Table 14. Total activities aborted metric

 Metadata Description 

 Metric Name ibm_db2_db_act_aborted 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Resource 
 Metric Description The total number of coordinator activities at any nesting level that completed with errors. 







 Total Activities Completed 



Table 15. Total activities completed metric

 Metadata Description
Click the Copy button to copy the token to your clipboard.

Do not share this API token. Anyone who has this API token has full access to your metrics.
5. The endpoint of your IBM Cloud Monitoring instance is per region. For example, if your IBM Cloud Monitoring instance exists in us-south, then its endpoint is:

https://us-south.monitoring.cloud.ibm.com/api/data/batch

The first part of the URL (in this example, us-south.monitoring.cloud.ibm.com) is your endpoint. Make note of this URL.
6. After you have both the API token and the endpoint, you can format your POST request. The following POST request is an example, with all the parameters that you can modify. The following are parameters:



* The Monitor API token.
* The endpoint of your IBM Cloud Monitoring instance.
* The value for ibm_is_vpn_server_name (the VPN server name that you want to see metrics for).



If you want to see this metric for all of your VPN servers, do not enter a value for the scope attribute. For example, use "scope" : "".



* The metric type that you want to see the results for. This example uses ibm_is_vpn_server_health_status.
* The from and to attributes define the timeframe to focus the scan, set in epoch time, and in microseconds.
* The sampling and value attributes set the granularity of the data that is returned in the POST request.





Because a large volume of data is stored in IBM Cloud Monitoring, choosing the specific level of granularity is important. IBM Cloud Monitoring can return only 600 data points at a time per request. As a result, the sampling and value attributes are important. Leaving these two lines out of your request returns an aggregate sum over that time period instead.

If the time range that is specified by from and to is large (for example, 4 days), but you define a sampling and value of 10 seconds, it means that you receive 4 days worth of data that is split into 10-second chunks.
The [region](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_overviewregistry_regions) in which a Container Registry or a Vulnerability Advisor metric is available corresponds to the region of the Container Registry that generated the metric.

The following table shows the location of Monitoring metrics.



Table 5. Location of Monitoring metrics

 Region for your account's registry Domain name of your registry Location of Monitoring metrics 

 ap-north jp.icr.io Tokyo (jp-tok) 
 ap-south au.icr.io Sydney (au-syd) 
 br-sao br.icr.io Sao Paulo (br-sao) 
 ca-tor ca.icr.io Toronto (ca-tor) 
 eu-central de.icr.io Frankfurt (eu-de) 
 jp-osa jp2.icr.io Osaka (jp-osa) 
 uk-south uk.icr.io London (eu-gb) 
 us-south us.icr.io Dallas (us-south) 



The following table shows the location of global registry Monitoring metrics.



Table 6. Location of global registry Monitoring metrics

 Registry Global registry Location of IBM Cloud Activity Tracker metrics 

 Global icr.io Washington (us-east) 









 Viewing metrics 

To monitor Container Registry metrics, you must start the Monitoring UI instance that is enabled for platform metrics in the region where you're using Container Registry.



 Starting the Monitoring UI from the Observability page 

To start the Monitoring UI from the Observability page, complete the following steps:



1. [Start the Monitoring UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch).
2. Select DASHBOARDS.
3. In the Default Dashboards section, expand IBM.
4. Choose the Container Registry dashboard from the list. Available dashboards are Container Registry Usage and Container Registry Quota Usage.