vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Used disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_messages_for_rabbitmq_disk_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used memory for an instance 

How much memory your deployment is using.



Table 11. Used memory for an instance metric metadata

 Metadata Description 

 Metric Name ibm_messages_for_rabbitmq_memory_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 









 Attributes for Segmentation 



 Global Attributes 

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



Table 12. Global Attributes Metadata

 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 might be a region, data center, or global. 
 Resource ibm_resource The resource being measured by the service - typically an identifying name or GUID. 
 Resource Type ibm_resource_type The type of the resource being measured by the service. 
 Scope ibm_scope The scope is the account, organization, or space GUID associated with this metric. 







 More Attributes 

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



Table 13. Additional Attributes Metadata

 Attribute Attribute Name Attribute Description 

 Service instance ibm_service_instance The service instance segment identifies the instance that the metric is associated with. 
 Service instance name ibm_service_instance_name The service instance name provides the user-provided name of the service instance, which isn't necessarily a unique value, depending on the name that is provided by the user. 
 Resource group ibm_resource_group_name The resource group where the service instance was created.
: Metrics are sent, based on the routing rule, on the defined route.

drop
: Metrics are excluded, based on the routing rule, when metrics are sent on the defined route.





 Inclusion filters 

Inclusion filters define the conditions that are used to determine which metrics are routed to the targets specified in the rule.

To route all metrics, exclude the inclusion_filters definition when you configure a route.

Inclusion filters are composed of an operand, operator, and value:

operand
: Operand is the name of the property in the target that is used to filter data. The following operands are supported: location, service_name, service_instance, resource_type, and resource. The value is extracted from the target CRN.

operator
: Two operators are supported: in and is.

in
: The value of the operand property is compared to a list of values.

You can define up to 20 values.

is
: The value of the operand property is compared to a single value.

When using is, only 1 value can be specified.

value
: A string, or an array of strings, to be compared with the operand property to determine whether the metric is routed or not. When the isoperator is used, value must include a single string. When the inoperator is used, value can include multiple strings in an array.

Valid values depend on the operand.

location
: Any location where [IBM Cloud Metrics Routing is available.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions)

service_name
: The CRN service name of an [IBM Cloud service that generates metrics managed through [IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-cloud-services-mr)

service_instance, resource_type, and resource
,"sigma":64,"width":1984},"pulse_shape":"gaussian_square","t0":0},{"ch":"m19","duration":1616,"name":"delay","t0":2240},{"duration":2240,"memory_slot":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"name":"acquire","qubits":0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26],"t0":0}]},{"name":"measure","qubits":20],"sequence":{"ch":"m20","label":"M_m20","name":"parametric_pulse","parameters":{"amp":0.2027627962022292,-0.24756261526380255],"duration":2240,"sigma":64,"width":1984},"pulse_shape":"gaussian_square","t0":0},{"ch":"m20","duration":1616,"name":"delay","t0":2240},{"duration":2240,"memory_slot":0,1,2,3,4,5,6,7,8,9
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Planning Analytics Hosted Globally Hosted Globally Hosted Globally Hosted Globally 
 Portfolio Optimization ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Predictive Market Scenarios ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) 
 Public Gateway ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/adcecdbe4e86955f88aac7f3c1e7ec3ff44992ef/icons/checkmark-icon.svg) !
Kafka quotas use sampling to determine how long clients should be paused before they can send or receive more data. For unpredictable workloads, or configurations that result in quota decisions being made using only a few samples, you might observe the percentage quota used metric going above 100%.



 Authentication failures 

Incrementing count of the number of authentication failures



Table 7. Authentication failures metric metadata

 Metadata Description 

 Metric Name ibm_eventstreams_kafka_authentication_failure_total 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Service instance name 



Ideally zero. A nonzero value on this indicates that clients attempt to connect by using invalid credentials. Ensure that all clients are using valid credentials.





 Consume message conversion time 

Indicates that the accumulated time spent performing message conversion from clients that are consuming by using older protocol versions.



Table 8. Consume message conversion time metric metadata

 Metadata Description 

 Metric Name ibm_eventstreams_instance_consume_conversions_time_quantile 
 Metric Type gauge 
 Value Type second 
 Segment By Service instance, Quantile, Service instance name 



Ideally zero, as nonzero indicates that clients are experiencing more latency because of using an older protocol level. Those clients are down-level and must be upgraded. Ensure that all clients are at the latest levels.





 Estimated connected clients percentage 

The percentage of maximum number of connected clients.



Table 9. Estimated connected clients percentage metric metadata

 Metadata Description 

 Metric Name ibm_eventstreams_kafka_recommended_max_connected_clients_percent 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance, Service instance name 



This is for information to help you monitor trends in your usage. See [Choosing your plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-plan_choose) to determine what the recommended limits are for your plan and cluster.





 Connected clients software name and version 

The number of connected clients with a particular client software name and version.



Table 10. Connected clients software name and version metric metadata

 Metadata Description
VPN server authentication failure count 

Number of authentication failures for a VPN server



Table 4: VPN server authentication failure count

 Metadata Description 

 Metric name ibm_is_vpn_server_authentication_failure_count 
 Metric type gauge 
 Value type none 
 Segment by Service instance, Service instance name, VPN server name 







 VPN server active client count 

Number of active clients for a VPN server



Table 5: VPN server active client count

 Metadata Description 

 Metric name ibm_is_vpn_server_active_client_count 
 Metric type gauge 
 Value type none 
 Segment by Service instance, Service instance name, VPN server name 







 VPN server health status 

Health status for a VPN server (for example, 2=ok, 1=degraded, 0=faulted/inapplicable)



Table 6: VPN server health status

 Metadata Description 

 Metric name ibm_is_vpn_server_health_status 
 Metric type gauge 
 Value type none 
 Segment by Service instance, Service instance name, VPN server name 









 Metric segmentation 

You can split the metrics that IBM Cloud Monitoring presents into various visualizations in the IBM Cloud Monitoring dashboard, allowing views of different metrics based on your preference. For example, if you have multiple VPN servers or accounts with different VPN servers in each account, you might want to focus on a particular VPN server by name.

As an example, you can segment the VPN Server Data Bytes Input by IBM VPN for VPC server name to show how many bytes per minute are received for a VPN server. The dashboard shows different lines in different colors where each line represents received bytes per minute for a VPN server.



 Global attributes 

The following attributes are available for segmenting all of the VPN server metrics:



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.
* [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)
* [Attributes for Segmentation](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsattributes-for-segmentation)
* [Default Dashboards](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsdefault-dashboards)
* [Setting Alerts](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsset-monitor-alerts)







 API reference 



 Key management service API 

[Hyper Protect Crypto Services key management service API change log](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-kms-api-change-logkms-api-change-log)



* [API versioning](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-kms-api-change-logkms-api-versioning)
* [February 2023](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-kms-api-change-logkms-api-Feb-2023)
* [January 2022](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-kms-api-change-logkms-api-jan-2022)
Check whether DevSecOps Toolchain collects software bills of materials (SBOM) to provide transparency in build artifacts CM-2(0), CM-2(1)(a), CM-2(1)(b), CM-2(1)(c), CM-2(2)(0), CM-2(3)(0), CM-3(2)(0), CM-3(e), CM-3(f), CM-8(1)(0), CM-8(2)(0), CM-8(a), CM-8(b), SA-10(a), SA-10(b), SA-15(a), SA-3(a), SA-3(d), SA-8(0), SI-2(2)(0), SI-2(a), SI-2(d), and SI-7(0) Rule was added 
 Check whether DevSecOps Toolchain signs build artifacts to attest their provenance CM-3(2)(0), SA-10(1)(0), SA-10(b), SA-10(c), SA-15(a), SA-3(a), SA-3(d), SA-8(0), SI-2(2)(0), SI-2(a), SI-2(d), and SI-7(0) Rule was added
* UI
* API







 Monitoring VPN gateway for VPC metrics 

IBM Cloud® Monitoring collects basic VPN metrics on IBM Cloud for VPC, such as VPN gateway status, VPN gateway packets input/output, and VPN connection bytes input/output. These metrics are stored in IBM Cloud Monitoring. You can access metrics through the prebuilt dashboard.



 Platform metrics overview 

You can view platform metrics when you enable IBM Cloud Monitoring on your IBM Cloud platform. An IBM Cloud Monitoring instance must be configured in a region to monitor these metrics. For more information, see [Enabling platform metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling).

Before you enable IBM Cloud Monitoring on your platform, keep the following information in mind:



* You can configure only one instance of the IBM Cloud Monitoring service per region to collect platform metrics.
* Metrics are collected automatically and are available for monitoring through the IBM Cloud Monitoring-enabled instance.
* Use the Metrics Router to allow customers to configure which IBM Cloud Monitoring instance their platform metrics flows to. To learn more about Metrics Router, see [IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router).







 Metrics available by service plan 

Metrics available by plan names are as follows:



* [VPN gateway total bytes input](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-monitoring-metricsibm_is_vpn_gateway_bytes_in)
* [VPN gateway total bytes output](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-monitoring-metricsibm_is_vpn_gateway_bytes_out)
* [VPN gateway total packets input](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-monitoring-metricsibm_is_vpn_gateway_packets_in)
The completion chart provides an overview of all the actions you have built and how many of these are being completed or not.

Completion is only applicable when a user question or request matched to an action, and the action starts.

One action can be triggered multiple times, so to better understand individual action performance, click Action completion to understand each action in more detail.





 Recognition 

Recognition is the measurement of how many requests are being recognized by the assistant and routed into starting an action.

The recognition chart provides you with a view into how many requests are matched to actions. This helps you to understand where you may have content gaps, where you might want to build new actions, or how existing actions aren't matching properly to user requests.

Customer requests are considered unrecognized if:



* The request triggers the No Action Matches action
* The assistant asks a clarifying question and the customer chooses None of the above



To get more detail, click on Unrecognized requests to review the requests that are not being recognized by the assistant, so you can create new actions that address questions and issues that aren't being answered.







 Most frequent, least frequent, and least completed 

These most/least cards help you to quickly identify specific actions that might need your attention. From these lists, you can click a specific action to do more analysis.

![Most frequent, least frequent, and least completed](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-most-least.png)

Most frequent actions shows the actions that have the most recognized requests matched with that action.

Least frequent actions is the exact opposite of most frequent. It can help you identify actions that possibly have poor training and are not matching well to actual requests from your users.

Least completed actions shows a list of actions with the lowest completion rate, by percentage. This measurement doesn't take traffic into account. This can be another good indication of actions where maybe the flow or content can be improved, and you can spend time investigating.
Metric Name ibm_databases_for_mysql_blocks_read_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Buffers backend rate 

Buffers backend rate



Table 4: Buffers backend rate metric metadata

 Metadata Description 

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







 Buffers checkpoint rate 

Buffers checkpoint rate



Table 5: Buffers checkpoint rate metric metadata

 Metadata Description 

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







 Cache hit ratio 

Cache hit ratio



Table 6: Cache hit ratio metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_cache_hit_ratio 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance 







 Deadlocks count 

Deadlocks count



Table 7: Deadlocks count metric metadata

 Metadata Description 

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







 Deadlocks rate 

Deadlocks rate



Table 8: Deadlocks rate metric metadata

 Metadata Description 

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







 Disk read latency mean 

Disk read latency mean



Table 9: Disk read latency mean metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_disk_read_latency_mean 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Disk write latency mean 

Disk write latency mean



Table 10: Disk write latency mean metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_disk_write_latency_mean 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 IO utilization in percent 5-minute average
Are metrics updated in real time? 

The most recent metrics can be updated every 5 minutes, while other metrics are updated every 24 hours.





 What is the time interval when you select Most recent from the Time frame list? 

The time range and time interval relationships are shown.



Table 2: Time range and time interval relationships

 Time range Time interval (minutes) 

 (0, 60] 1 
 (60, 300] 5 
 (300, 600] 10 
 (600, 900] 15 
 (900, 1200] 20 
 (1200, 1500] 25 
 (1500, 1800] 30 
 (1800, 2100] 35 
 (2100, 2400] 40 
 (2400, 2700] 45 
 (2700, 2880] 50 



Math notation ( means "does not include" and ] means "include".

Example: Start Date timestamp: 1611244800 End Date timestamp: 1611248400 Time range = (End Date timestamp - Start Date timestamp) / 60 = 300 Referring to the preceding table, the time interval is 5 minutes.





 Why does the last point sometimes drop suddenly in the Most Recent Metrics Report? 

Zoom

![Most recent interval](https://cloud.ibm.com/docs-content/v1/content/006fd22ab2811b7d19804c763a00568b3da4c03a/CDN/images/metrics-most-recent-interval.png)

Figure 7: Most recent interval

In the report, each point is a sum of metric data over a time interval, and the interval is calculated by the preceding table. However, for the last point, the interval might be smaller than others. For example, in the bandwidth "most recent" report, the time interval is 5 minutes, and all the points are the sum of bandwidth over 5 minutes, except that the last one is only 1-minute bandwidth (January 21 04:00 PM to January 21 05:00 PM).
[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.



* If you collect metrics through the Monitoring service, you must launch the Monitoring UI for the instance that is either enabled for platform metrics in the same region as your service instance or is configured as a Metrics Router target.
* If you collect and route metrics to 1 or more Monitoring instances by configuring IBM Cloud Metrics Routing in the account, you must launch the Monitoring UI for each instance that is configured and included in a routing rule.



In Monitoring, use the IBM Cloud Metrics Routing Overview predefined dashboard template to monitor IBM Cloud Metrics Routing in IBM Cloud.

To open the predefined IBM Cloud Metrics Routing template, complete the following steps from the Monitoring UI:



1. In the Monitoring UI, go to Dashboards > Dashboard templates > IBM.
2. Select IBM Cloud Metrics Routing Overview.



You cannot modify a dashboard template. However, you can copy the template and create a custom dashboard that you can then configure.

Next, choose any of the following tasks to learn more about how to manage and work with platform metrics:



Table 5. More information about Monitoring tasks

 Task For more information 

 Working with platform metrics [link](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_working) 
 Controlling what data is visible [link](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingcontrolling-what-data-is-visible) 
 Monitoring metrics using dashboards [link](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingplatform_metrics_working_dash)
Segment By Service instance, name of the namespace, project name, the jobrun condition 









 Attributes for segmentation 



 Global Attributes 

The following attributes are available for segmenting all the metrics previously listed.



Table 17: Global attributes

 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, which can be a region, data center, or global. 
 Resource ibm_resource The resource that is measured by the service, which is typically an identifying name or GUID. 
 Resource Type ibm_resource_type The type of the 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 is the account, organization, or space GUID associated with this metric. 
 Service name ibm_service_name Name of the service that is generating this metric. 







 More attributes 

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



Table 18: Segmentation options

 Attribute Attribute Name Attribute Description 

 Name of the namespace ibm_codeengine_namespace Name of the namespace. This unique identifier is contained in the URL of your application. The default URL for applications is of the format https://<appname>.<uuid>.<region>.codeengine.appdomain.cloud where appname is the name of your application, uuid is the automatically generated unique identifier, and region is the region in which your Code Engine project resides. The UUID portion of the URL is the name of the namespace. 
 Service instance ibm_service_instance The service instance segment identifies the instance that the metric is associated with. 
 HTTP status code ibm_codeengine_status HTTP status code. 
 Application name ibm_codeengine_application_name Name of the application. 
 Application revision name ibm_codeengine_revision_name Name of the application revision. 
 Gateway instance ibm_codeengine_gateway_instance The gateway instance.