vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* The skill's analytics feature uses this node to learn about the topics that your dialog can't address. The coverage metric looks for occurrences of nodes with the anything_else condition being processed in the user conversation logs. It uses this information to determine the frequency with which your dialog is able to match user requests to intents that can address them. The node is registered by the metric if it conditions on anything_else alone or when it's used in combination with another condition, such as anything_else && positive_feedback.

For more information about the coverage metric, see [Graphs and statistics](https://cloud.ibm.com/docs/assistant?topic=assistant-logs-overviewlogs-overview-graphs).
* If you want your assistant to redirect queries to the search skill when the dialog is unable to address them, this node recognizes when it's time to initiate the search. It's when a customer's message reaches the anything_else node that the message is sent to the search skill to find a relevant answer in your configured data collections. For more information about searching for an answer, see [Search triggers](https://cloud.ibm.com/docs/assistant?topic=assistant-skill-search-addskill-search-add-trigger).

Messages that trigger search in this way are still registered by the coverage metric as messages that are not covered.
3","qubits":0],"sequence":{"ch":"d0","name":"fc","phase":"-(P2)","t0":0},{"ch":"d0","label":"X90p_d0","name":"parametric_pulse","parameters":{"amp":0.10251500297795856,0.0013875720342836051],"beta":-0.13421884846658816,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0},{"ch":"d0","name":"fc","phase":"-(P0)","t0":160},{"ch":"d0","label":"X90m_d0","name":"parametric_pulse","parameters":{"amp":-0.10251500297795856,-0.0013875720342836056],"beta":-0.13421884846658816,"duration":160,"sigma":40},"pulse_shape":"drag","t0":160},{"ch":"d0","name":"fc","phase":"-(P1)","t0":320},{"ch":"u1","name":"fc","phase":"-(P2)","t0":0},{"ch":"u1","name
* endDate - Provide the end date timestamp (UTC+0) for query.
* frequency - Provide the data frequency for data format, the following options are available to configure frequency:



* aggregate - Aggregated metrics data from startDate to endDatedefault.
* day - Daily metrics data from startDate to endDate.





* Return - A collection of objects of type SoftLayer_Container_Network_CdnMarketplace_Metrics.



--------------------





 getMappingBandwidthByRegionMetrics 

Returns the total number of predetermined statistics for direct display (no graph) for a given mapping, over a given period of time. The value of frequency is aggregate by default.



* Parameters:



* mappingUniqueId - Provide a unique ID of the mapping for which metrics are queried.
* startDate - Provide the start date timestamp (UTC+0) for query.
* endDate - Provide the end date timestamp (UTC+0) for query.
* frequency - Provide the data frequency for data format, the following options are available to configure frequency:



* aggregate - Aggregated metrics data from startDate to endDatedefault.
* day - Daily metrics data from startDate to endDate.





* Return - A collection of objects of type SoftLayer_Container_Network_CdnMarketplace_Metrics.



--------------------





 getCustomerRealTimeMetrics 

Returns the real-time metrics for the current account, including the total data (bandwidth and hits) over the given period of time and the detailed data divided with the given time interval. For more details, [View the examples](https://cloud.ibm.com/docs/CDN?topic=CDN-code-examples-using-the-cdn-apiexample-code-for-getting-real-time-metrics).



* Parameters:



* vendorName - The name of the CDN provider. Currently, only akamai is supported.
VPC virtual server instances metrics definitions 

The following tables define basic VPC virtual server instance metrics.



 CPU monitoring metrics 



 Average CPU usage percentage 

The 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 2, resource name 







 CPU usage 

The cumulative total of 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 2, resource name, Virtual CPU index 







 CPU usage percentage 

The 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 2, resource name, Virtual CPU index 







 Total CPU usage 

The cumulative time that is elapsed running instructions across all CPUs since virtual server instance start.



Table 4: Total CPU usage metric metadata

 Metadata Description 

 Metric name ibm_is_instance_total_cpu_usage_nanoseconds 
 Metric type gauge 
 Value type second 
 Segment by IBM IS Generation 2, resource name 







 Total number of CPUs 

The total number of CPUs.



Table 5: Total number of CPUs metric metadata

 Metadata Description 

 Metric name ibm_is_instance_cpus 
 Metric type gauge 
 Value type none 
 Segment by IBM IS Generation 2, resource name 









 Network monitoring metrics 



 Bytes received for a network interface 

The cumulative number of bytes received for a network interface since virtual server instance start.



Table 6: Average CPU usage percentage metric metadata

 Metadata Description 

 Metric name ibm_is_instance_network_in_bytes 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation 2, resource name, MAC address of the network interface 







 Bytes sent for a network interface
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/icons/checkmark-icon.svg) 
 [Git Repos and Issue Tracking](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-grit) hostedgit 
 [GitHub](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-github) githubconsolidated 
 [GitLab](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-gitlab) gitlab 
 [HashiCorp Vault](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-hashicorpvault) hashicorpvault 
 [Jenkins](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-jenkins) jenkins 
 [JIRA](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-jira) jira 
 [Key Protect](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-keyprotect) keyprotect 
 [Nexus](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-nexus) nexus 
 [Other Tool](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-othertool) customtool 
 [PagerDuty](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-pagerduty) pagerduty
[Checkmark](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker//images/checkmark-icon.svg) [Location-based events](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-at_events) 
 [IBM Watson® Studio](https://dataplatform.cloud.ibm.com/docs/content/wsj/getting-started/overview-ws.html) data-science-experience ![Checkmark](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker//images/checkmark-icon.svg) [Location-based events](https://dataplatform.cloud.ibm.com/docs/content/wsj/admin/at-events.htmlws) 
 [IBM Watson™ Knowledge Catalog](https://dataplatform.cloud.ibm.com/docs/content/wsj/catalog/overview-wkc.html) datacatalog ![Checkmark](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker//images/checkmark-icon.svg) [Location-based events](https://dataplatform.cloud.ibm.com/docs/content/wsj/admin/at-events.htmlwkc) 
 [IBM Watson® Knowledge Studio](https://cloud.ibm.com/docs/watson-knowledge-studio) knowledge-studio !
Run the following command to view the peer metrics. To view the orderer metrics you would run the same command but replace the <peer-endpoint> with the <orderer-endpoint>.

curl -k <peer-endpoint>/metrics --cert <client-tls-cert> --key <client-tls-key> --cacert <peer tls ca-cert>

For example:

curl -k https://169.55.231.152:30766/metrics --cert msp/org1/ca/tls/msp/signcerts/cert.pem --key msp/org1/ca/tls/msp/key.pem --cacert msp/org1/ca/tls/msp/cacerts/tlsca.pem

For more information about metrics, see [Metrics](https://hyperledger-fabric.readthedocs.io/en/release-2.2/operations_service.htmlmetrics).





 Viewing logging levels 

Run the following command to view the logging level. You will see the log level on your terminal after the command completes.

curl -k <peer-endpoint>/logspec --cert <client-tls-cert> --key <client-tls-key> --cacert <peer tls ca-cert>

For example:

curl -k https://169.46.208.93:3210/logspec --cert msp/org1/ca/tls/msp/signcerts/cert.pem --key msp/org1/ca/tls/msp/keystore/key.pem --cacert msp/org1/ca/tls/msp/cacerts/tlsca.pem

You can see the result that is similar to the following example:

{"spec":"info"}





 Setting logging levels 

To change the existing logging level setting, run the following command, which uses the PUT method with JSON body that consists of a single attribute named spec.
[Topic size](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metricsibm_eventstreams_instance_topic_size) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/icons/checkmark-icon.svg) 







 Enhanced metrics available with consumers enabled 



Table 4. Metrics available for consumers

 Metric name Enterprise Lite Standard 

 [Consumer groups lag](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metricsibm_eventstreams_instance_consumer_groups_lag) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/icons/checkmark-icon.svg) 







 Enhanced metrics available with partitions enabled 



Table 5. Metrics available for partitions

 Metric name Enterprise Lite Standard 

 [Message rate per partition](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metricsibm_eventstreams_instance_message_rate_per_partition) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/icons/checkmark-icon.svg) 



This information is useful to detect if the distribution of message activity across the partitions in a topic is not balanced and if the number of partitions a topic has is scaled appropriately.





 Metrics available with quotas enabled 



Table 6. Metrics available for quotas

 Metric name Enterprise Lite Standard
* Matches the host_cpu_used_percent non-information metric to the filtered sysdig_cloud_provider_info information metric when the host_mac label has the same value. The values are multiplied, but because the information metric has a value of 1, the result is unchanged. The region and account labels are added to the resulting data.
* Calculates the average of the new metrics by account and region.









 cURL sample to extract latest metric 

To get the latest value of a metric, specify only the metric name. The most recent value that was generated no more than 5 minutes ago is returned.

For instance, to get the latest value of host_cpu_used_percent:

curl <SYSDIG_REST_API_ENDPOINT>/prometheus/api/v1/query?query=sysdig_host_cpu_used_percent -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "SysdigTeamID: $TEAM_ID" -H "content-type: application/json"

Where



* <SYSDIG_REST_API_ENDPOINT>indicates the endpoint targetted by the REST API call. For more information, see [Monitoring REST API endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_rest_api). For example, the public endpoint for an instance that is available in us-south is the following: https://us-south.monitoring.cloud.ibm.com/api
* You can pass multiple headers by using -H.

Authorization and IBMInstanceID are headers that are required for authentication.

SysdigTeamID is optional. When you specify this header, you limit the request to the data and resources available for the team specified.

To get an AUTH_TOKEN and the GUID see, [Headers for IAM Tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curlmon-curl-headers-iam).



All dashboards support the full PromQL API.
{
"processing_metrics": {
"processed_audio": {
"received": 7.04,
"seen_by_engine": 2.59,
"transcription": 1.25,
"speaker_labels": 0.0
},
"wall_clock_since_first_byte_received": 0.57,
"periodic": true
}
}
. . .
Show more





 Processing metrics example: Asynchronous HTTP interface 

The following example shows a speech recognition request for the /v1/recognitions method of the asynchronous HTTP interface. The request enables processing metrics and specifies an interval of 0.25 seconds. The audio file again includes the message "hello world long pause stop".

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: audio/flac" --data-binary @{path}audio-file.flac "{url}/v1/recognitions?processing_metrics=true&processing_metrics_interval=0.25"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: audio/flac" --data-binary @{path}audio-file.flac "{url}/v1/recognitions?processing_metrics=true&processing_metrics_interval=0.25"

The following example output shows the first two processing metrics results that the service returns for the request.

{
"processing_metrics": {
"processed_audio": {
"received": 7.04,
"seen_by_engine": 1.59,
"transcription": 0.49
},
"wall_clock_since_first_byte_received": 0.32,
"periodic": true
}
}
{
"processing_metrics": {
"processed_audio": {
"received": 7.04,
[External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.youtube.com/watch?v=nTzrA56zLTE&cm_sp=Developper-_-enrich-multi-media-files-using-ibm-watson-_-View-the-Video)







 Analyze SMS messages with Watson Knowledge Studio 

Build a custom model to better categorize SMS message content using Watson Knowledge Studio and Watson Natural Language Understanding.



* [Learn more ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/patterns/analyze-sms-messages-with-watson-knowledge-studio/)
* [Get the Code ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://github.com/IBM/sms-analysis-with-wks?cm_sp=Developer-_-analyze-sms-messages-with-watson-knowledge-studio-_-Get-the-code)
* [View the Demo ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://youtu.be/lwW97UQj0RM?cm_sp=Developer-_-analyze-sms-messages-with-watson-knowledge-studio-_-Watch-the-Video)







 Correlate documents from different sources 

Correlate content across documents by using the Python NLTK and IBM Data Science Experience.



* [Learn more ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://developer.ibm.com/patterns/watson-document-correlation/)
* [Get the Code !
Read the description for each visualization, then choose the one that best meets your requirements.

Line ("View trends over time") is the easiest and most basic option. It is also the most frequently selected option. The following examples show a Line-based visualization.
5. Configure your custom dashboard.



* In the Metrics field, enter ibm_cloud to display the IBM IBM Cloud Monitoring load balancer metrics. The ones discussed so far in this topic are ibm_cloud_load_balancer_active_connections, ibm_cloud_load_balancer_connection_rate, and ibm_cloud_load_balancer_throughput. After you click and add each metric, a new dropdown menu appears to select the next one. Repeat this process until you added all three.



You can monitor listener port traffic by enabling the ibm_cloud_load_balancer_listener_port metric.



* You can choose a scope to display in your dashboard by clicking Override Dashboard Scope. For example, you can display the metrics for a particular load balancer.
* You can also set a segment to compare metrics across the scope you defined. For example, you can look at throughput for a particular load balancer segmented by listener port.



6. Click Save for your new custom dashboard to be accessible.

By default, the dashboard begins with the name "blank dashboard". You can change the name by selecting Dashboards from the sidebar, then clicking the Pencil icon next to the name.



To return to the default IBM Cloud Monitoring dashboard at any time, select Dashboards > Default Dashboards > IBM > Load Balancer Monitoring Metrics.





 Working with IBM Cloud Monitoring using the APIs 

You can also work with the IBM Cloud Monitoring instance by using the metric query API. You might want to do this if you need raw data points or want to consume your metrics from a command-line interface rather than using the IBM Cloud Monitoring dashboard.

After you create your IIBM Cloud Monitoring instance, you must collect the following two pieces of information.



* The IBM Cloud Monitoring Monitor API token
* The endpoint of your IBM Cloud Monitoring IBM Cloud Monitoring instance
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 sysdig-monitor.metrics-descriptors.read View metrics descriptors. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) 
 sysdig-monitor.notification-channels.edit Edit notification channels. ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/checkmark-icon.svg) !
Segment by Application load balancer appliance metrics and Application load balancer listener metrics 







 HTTP 3xx response code count 

The HTTP 3xx response code count is the count of all HTTP response codes in the 300-399 range received from the back-end per minute. This metric is only available for HTTP and HTTPS listeners.



Table 7: Application load balancer HTTP 3xx response count metric metadata

 Metadata Description 

 Metric name ibm_is_load_balancer_backend_http_3xx 
 Metric type gauge 
 Value type none 
 Segment by Application load balancer appliance metrics and Application load balancer listener metrics 







 HTTP 4xx response code count 

The HTTP 4xx response code count is the count of all HTTP response codes in the 400-499 range that is received from the back-end per minute. This metric is only available for HTTP and HTTPS listeners.



Table 8: Application load balancer HTTP 4xx response count metric metadata

 Metadata Description 

 Metric name ibm_is_load_balancer_backend_http_4xx 
 Metric type gauge 
 Value type none 
 Segment by Application load balancer appliance metrics and Application load balancer listener metrics 







 HTTP 5xx response code count 

The HTTP 5xx response code count is the count of all HTTP response codes in the 500-599 range that is received from the back-end per minute. This metric is only available for HTTP and HTTPS listeners.



Table 9: Application load balancer HTTP 5xx response count metric metadata

 Metadata Description 

 Metric name ibm_is_load_balancer_backend_http_5xx 
 Metric type gauge 
 Value type none 
 Segment by Application load balancer appliance metrics and Application load balancer listener metrics 







 Total Members 

The total members count is the number of members created in a pool. This metric is only available for TCP, HTTP, and HTTPS listeners.



Table 10: Application load balancer total members count metric metadata

 Metadata Description 

 Metric name ibm_is_load_balancer_backend_total_members 
 Metric type gauge 
 Value type none
Segment By [Attributes for Segmentation](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-operational-metricsattributes-for-segmentation) 







 Attributes for Segmentation 

You can filter your metrics by using the following attributes.



Table 3. Describes the attributes use for segmenting metrics.

 Attribute Name Description 

 ibm_resource_type Supported resource type is instance. 
 ibm_hpcs_response_code Response code for the Hyper Protect Crypto Services service API request. 
 ibm_scope The account, organization, or space GUID associated with the metric. 
 ibm_ctype Public, dedicated, or local. 
 ibm_location Location of the Hyper Protect Crypto Services service instance. 
 ibm_service_name kms. 
 ibm_resource Hyper Protect Crypto Services service instance ID. 
 ibm_hpcs_api Hyper Protect Crypto Services service API name. 
 ibm_resource_group_name Resource group name associated with the Hyper Protect Crypto Services service instance. 
 ibm_service_instance_name Hyper Protect Crypto Services service instance name. 
 ibm_service_instance Hyper Protect Crypto Services service instance ID. 







 Default Dashboards 

You need to configure platform metrics and enable a [metrics policy](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-monitoring-metrics) on your service instance in order to view your Hyper Protect Crypto Services operational metrics dashboard.



 How to find the Monitoring dashboard for your Hyper Protect Crypto Services service instance by using Hyper Protect Crypto Services console 

After you configure your Monitoring instance to receive platform metrics, complete the following steps:



1. [Provision your Hyper Protect Crypto Services instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-provisionprovision-gui).
2. On your Hyper Protect Crypto Services instance page, click Actions > Monitoring. On your first usage, you might see a welcome wizard. To advance to the dashboard selection menu, select Next and then Skip at the bottom of the Choosing an installation method page.
IBM Cloud Monitoring sysdig-monitor Consolidate time series data to the region of your primary operations. 



The following table outlines the locations where you can configure IBM Cloud Metrics Routing to collect and manage metrics:



Table 2. Supported locations

 Geo Region IBM Cloud Metrics Routing 

 Asia Pacific Chennai (in-che) 
 Asia Pacific Tokyo (jp-tok) 
 Asia Pacific Seoul (kr-seo) 
 Asia Pacific Sydney (au-syd) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/metrics-router/images/checkmark-icon.svg) 
 Asia Pacific Osaka (jp-osa) 
 Europe Frankfurt (eu-de) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/metrics-router/images/checkmark-icon.svg) 
 Europe London (eu-gb) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/metrics-router/images/checkmark-icon.svg) 
 North America Dallas (us-south) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/dad8f28785f0dc036aaae4b777787e73db9ff0d4/metrics-router/images/checkmark-icon.svg) 
 North America Washington DC (us-east) !