vania-janet/multiturn-rag-retrieval-data huggingface dataset:
(https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/dashboard_link.png)

Figure 3. IBM Cloudant Dashboard

Next, change the scope or make a copy of the Default dashboard to monitor an IBM Cloudant instance.









 IBM Cloudant metrics dictionary 



 HTTP request count 

The number of HTTP requests made against an IBM Cloudant instance:



Table 2. HTTP request count metric metadata

 Metadata Description 

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







 Rate-limited operations 

The number of operations that were rate-limited:



Table 3. Rate-limited operations metric metadata

 Metadata Description 

 Metric Name ibm_cloudant_rate_limited_operations 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, Service instance name, Cloudant operation type 









 Attributes for segmentation 



 Global Attributes 

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



Table 4. Global attributes

 Attribute Name 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, typically an identifying name, or GUID. 
 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 generates this metric. 







 More 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 in the following table:



Table 5. More attributes

 Attribute Name Description 

 Cloudant operation type ibm_cloudant_operation_type The Cloudant billable operation type. 
 Service instance ibm_service_instance The service instance segment identifies the instance that the metric is associated with.
Scope ibm_scope The extent of the data samples that are considered. You can choose the scope to be the account, an organization, or a space GUID that is associated with this metric. 
 Service name ibm_service_name Name of the service that generates this metric. toolchain 







 Additional attributes 

The following attributes are available for segmenting one or more global attributes:

Check each individual metric for the supported segmentation options.



Table 7. Additional segmentation attributes

 Attribute Attribute Name Attribute Description 

 Private worker pool ibm_toolchain_pipeline_worker_pool The unique id of a Continuous Delivery pipeline private worker pool.
Table 8. IOPS read and write total count for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_disk_iops_read_write_total 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Max allowed memory for an instance 

The maximum amount of memory available to your deployment.



Table 9. Max allowed memory for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_memory_limit_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 The total number of connections in use 

The total number of connections in use.



Table 10. The total number of connections in use metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_total_connections 
 Metric Type gauge 
 Value Type count 
 Segment By Service instance 







 Total disk space for an instance 

Represents the total amount of disk available to your deployment.



Table 11. Total disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_disk_total_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used CPU for an instance 

How much CPU is used as a percentage of total CPU available.



Table 12. Used CPU for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_cpu_used_percent 
 Metric Type gauge 
 Value Type percent 
 Segment By Service instance 







 Used disk space for an instance 

How much disk your deployment is using.



Table 13. Used disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_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 14. Used memory for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases-for-cassandra_memory_used_bytes 
 Metric Type gauge 
 Value Type byte 
 Segment By Service instance 







 Used JVM heap percent
[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 

 [IAM ID bytes in quota used percentage](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metricsibm_eventstreams_iam_id_bytes_in_quota_used_percentage) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/icons/checkmark-icon.svg) 
 [IAM ID bytes out quota used percentage](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metricsibm_eventstreams_iam_id_bytes_out_quota_used_percentage) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/e0c3acba1296ff980e76d5db456d53adefaabba4/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
* Built-in Prometheus and Grafana deployments in the openshift-monitoring project for cluster metrics.
* At-a-glance, real-time view of how your pods consume cluster resources that can be accessed from the Red Hat OpenShift Cluster Console.
* Monitoring is on a per-cluster basis.
* The openshift-monitoring project stack is set up in a single zone only. No persistent storage is available to back up or view metric history.
* In cluster versions 4.10 and later an AuditWebhookError alert was added that fires when the audit webhook crashes or is deleted. For more information, see [Viewing the AuditWebhookError alert](https://cloud.ibm.com/docs/openshift?topic=openshift-health-auditaudit-webhook-error-410).



For more information, see [Monitoring](https://docs.openshift.com/container-platform/4.11/monitoring/monitoring-overview.html).





 Monitoring Red Hat® OpenShift® on IBM Cloud® storage metrics 

Red Hat® OpenShift® on IBM Cloud® clusters include built-in tools to help cluster administrators get information about the availability and capacity of storage volumes.

If you are unable to view storage metrics in the Red Hat OpenShift monitoring dashboard, see [Debugging Block Storage for VPC metrics](https://cloud.ibm.com/docs/containers?topic=containers-debug_monitoring).

The following metrics can be monitored for Red Hat® OpenShift® on IBM Cloud® clusters.



* kubelet_volume_stats_available_bytes
* kubelet_volume_stats_capacity_bytes
* kubelet_volume_stats_inodes
* kubelet_volume_stats_inodes_free
* kubelet_volume_stats_inodes_used



Want to set up storage monitoring alerts for platforms such as email or Slack?
_summary](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_posture_scans_summary)<br> * [ibm_scc_posture_scope](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_posture_scope)<br> * [ibm_scc_posture_scope_correlation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_posture_scope_correlation)<br> * [ibm_scc_posture_scopes](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_posture_scopes)<br> * [ibm_scc_si_note](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_si_note)<br> * [ibm_scc_si_notes](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_si_notes)<br> * [ibm_scc_si_occurrence](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_si_occurrence)<br> * [ibm_scc_si_occurrences](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_si_occurrences)<br> * [ibm_scc_si_providers](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/scc_si_providers)<br><br><br> 







 Transit Gateway 



 Resources Data sources
From the Manage page, click Actions > Add monitoring to configure platform metrics in the region of your Continuous Delivery instance.

If the menu choices include the Monitoring option, then the account and region that contain the Continuous Delivery instance is already configured for platform metrics.
5. Provision an instance of the IBM Cloud Monitoring service.

After you provision the Monitoring instance, the Observability page opens. To continue working with Continuous Delivery, go back to the Continuous Delivery UI.



Metrics are not visible until you [set up your Tekton pipelines](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines), configure at least one [private worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-install-private-workers) pool, and trigger some [Tekton pipeline triggers](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelinesconfigure_tekton_pipeline) to generate the queue time metric.





 Viewing metrics 

To monitor Continuous Delivery metrics, you must launch the Monitoring web UI instance that is enabled for platform metrics in the region where your Continuous Delivery instance is available.

There are different options to launch the Monitoring web UI and monitor metrics:



 Launching the Monitoring web UI from the Continuous Delivery dashboard 

Complete the following steps to launch the Monitoring web UI from the Continuous Delivery dashboard:



1. Log in to IBM Cloud.
2. Click Resource list.
3. In the Services and software section, click the Continuous Delivery instance that you plan to monitor.
4. From the Manage page, click Actions > Monitoring to view the Continuous Delivery dashboard within the context of your Continuous Delivery instance.







 Launching the Monitoring web UI from the Observability page 

Complete the following steps to launch the Monitoring web UI from the Observability page:



1. [Launch the Monitoring web UI](https://cloud.ibm.com/docs/Monitoring-with-Sysdig?topic=Monitoring-with-Sysdig-launch).
Each attachment must point to an existing file, and each attachment name must be unique (that is, --attachment a/foo.json --attachment b/foo.json is not permitted).
* --issue: list of issue URLs, which can be used to track activities that are related to the findings. The flag can be passed multiple times.
* --scope: a unique identifier that can be used to correlate evidence from multiple sources.
* --comment-on-issues: add a comment with details about the created evidence to the incident issues provided by using --issue flag



* Since the issues can be either on github, the provider is parsed from the issue URLs
* Every issue must be from the same repository
* The issue urls must match the following pattern:



* https://<host>/<owner>/<name>/issues/<issue number> - for github



* Required environment variables to access the issues repository:



* if the urls point to github issues:



* GH_URL: optional, defaults to https://github.ibm.com/api/v3
* GHE_TOKEN









Some environment variables are automatically picked up to add details about the asset origin:



* Setting TOOLCHAIN_CRN is the same as specifying --origin toolchain_crn=$TOOLCHAIN_CRN
* Setting PIPELINE_ID is the same as specifying --origin pipeline_id=$PIPELINE_ID
* Setting PIPELINE_RUN_ID is the same as specifying --origin pipeline_run_id=$PIPELINE_RUN_ID



The behavior of the command can be altered by using these flags:



* --dry-run: Adds nothing to the locker, but shows what would be added.
* --cache-mode: Similar to dry-run. Doesn't actually add the evidence to the locker, but adds the attachments (if any) to the locker. Shows the evidence that would be added.
* --format: controls the output format, id or json (id by default).
,"phase":"-(P1)","t0":0},{"ch":"d4","label":"Y90p_d4","name":"parametric_pulse","parameters":{"amp":-0.0010006507509606616,0.09398545949749511],"beta":-0.8252889412167893,"duration":160,"sigma":40},"pulse_shape":"drag","t0":0},{"ch":"d4","name":"fc","phase":"-(P0)","t0":160},{"ch":"u13","name":"fc","phase":"-(P1)","t0":0},{"ch":"u13","name":"fc","phase":"-(P0)","t0":160},{"ch":"u3","name":"fc","phase":"-(P1)","t0":0},{"ch":"u3","name":"fc","phase":"-(P0)","t0":160}]},{"name":"u2","qubits":5],"sequence":{"ch":"d5","name":"fc","phase":"-(P1)","t0":0},{"ch":"d5","label":"Y90p
The number of concurrent invocations on the system.



Table 3: Concurrent invocations metric metadata

 Metadata Description 

 Metric Name ibm_functions_concurrent_invocations 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance, ibm_functions_namespace, ibm_functions_package, ibm_functions_action 







 ibm_functions_concurrent_rate_limit 

The sum of activations that were throttled due to exceeding the concurrency rate limit.



Table 4: Concurrent rate limit metric metadata

 Metadata Description 

 Metric Name ibm_functions_concurrent_rate_limit 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, ibm_functions_namespace, ibm_functions_package, ibm_functions_action 







 ibm_functions_duration 

The average action duration, billed action execution time in milliseconds.



Table 5: Duration metric metadata

 Metadata Description 

 Metric Name ibm_functions_duration 
 Metric Type gauge 
 Value Type second 
 Segment By Service instance, ibm_functions_namespace, ibm_functions_package, ibm_functions_action 







 ibm_functions_init_time 

The time that is spent to initialize the action container in milliseconds.



Table 6: Initial time metric metadata

 Metadata Description 

 Metric Name ibm_functions_init_time 
 Metric Type gauge 
 Value Type second 
 Segment By Service instance, ibm_functions_namespace, ibm_functions_package, ibm_functions_action 







 ibm_functions_status_error_application 

The number of unsuccessful activations that are caused by application errors.



Table 7: Application errors metric metadata

 Metadata Description 

 Metric Name ibm_functions_status_error_application 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, ibm_functions_namespace, ibm_functions_package, ibm_functions_action 







 ibm_functions_status_error_developer 

The number of unsuccessful activations that are caused by the developer.



Table 8: Developer errors metric metadata

 Metadata Description 

 Metric Name ibm_functions_status_error_developer 
 Metric Type counter 
 Value Type none 
 Segment By Service instance, ibm_functions_namespace, ibm_functions_package, ibm_functions_action
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.



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 Red Hat OpenShift or host level metrics.

This tab is only available for users that belong to a team that has access to monitor Red Hat OpenShift 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).



 Before you begin 



1. [Read about IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started).
2. Install the IBM Cloud CLI. For more information, see [Installing the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
3.
You can also find a graphical representation of Total Bandwidth, Total Hits, and Hits By Type.

Zoom

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

Figure 5: Most recent graphs

You can view data for the past 48 hours only.







 FAQs for metrics report 



 Is there a minimum number of days for which I can view metrics? Is there a maximum? 

There is a minimum and maximum number of days for which you can view metrics by using IBM Cloud® Content Delivery Network with Akamai. Historical metrics can be gathered for a minimum of 1 day and a maximum of 90 days. Most recent metrics can be gathered for a minimum of 1 minute and a maximum of 48 hours.





 Why is the hit ratio nonzero when total hits are zero? 

Hit ratio represents the percentage of times the content was delivered from the Edge server cache, rather than being delivered from the origin server. It is calculated as follows:

((Edge hits - Ingress hits)/Edge hits)* 100

Where:

Edge hits specifies all hits to the Edge servers from the users. Ingress hits specifies origin or ingress hits for traffic from your origin server to Akamai Edge servers.

Because Hit Ratio is calculated at the account level and not per CDN, the Hit Ratio is the same for all the CDNs in your account. This fact also explains why the Hit Ratio might be nonzero when the number of Edge hits for a particular CDN is zero.





 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
)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingplatform_metrics_working_dash)[![Configuring an alert on a platform metric](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_4.svg)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingplatform_metrics_working_alert)[![Controlling access by using teams](https://cloud.ibm.com/docs-content/v1/content/bcd8b79ca2ed73bfcaefb20051f12cb6400286ab/atracker/images/platform_metrics_task_5.svg)](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_workingplatform_metrics_working_team)





 Metrics 

Activity Tracker Event Routing exposes the following metrics:



* [Total number of events successfully sent to the storage target](https://cloud.ibm.com/docs/atracker?topic=atracker-monitoring_metricsibm_atracker_successful_events_by_target)
* [Total number of events that failed to send to the storage target](https://cloud.ibm.com/docs/atracker?topic=atracker-monitoring_metricsibm_atracker_failed_events_by_target)
* [Total number of events that are discarded](https://cloud.ibm.com/docs/atracker?topic=atracker-monitoring_metricsibm_atracker_discarded_events)





 Total number of events successfully sent to the storage target 

Total number of events that are successfully sent to the storage target.



Table 1. Total number of events successfully sent to the storage target

 Metadata Description
(https://cloud.ibm.com/docs-content/v1/content/0bc8db34a3d90b2a5103c9c71b08a96de9525bbc/key-protect/images/monitor-dashboard-menu.png)

Figure 2. The dashboard menu that lists the dashboards in your Monitoring instances.

Below are figures that show the metric views available to you on the default dashboard.

Zoom

![An example of a Key Protect metrics dashboard.](https://cloud.ibm.com/docs-content/v1/content/0bc8db34a3d90b2a5103c9c71b08a96de9525bbc/key-protect/images/monitor-operation-dash1.png)

Figure 3. Some of the metrics available on the Monitoring dashboard.

Zoom

![An example of a Key Protect dashboard view.](https://cloud.ibm.com/docs-content/v1/content/0bc8db34a3d90b2a5103c9c71b08a96de9525bbc/key-protect/images/monitor-operation-view2.png)

Figure 4. Some of the metrics available on the Monitoring dashboard.

You will not be able to see any metrics in your Monitoring instance until you enable a metrics policy for your Key Protect instance and make API requests to your Key Protect instance.







 Setting Alerts 

You can set alerts on your Monitoring dashboard to notify you of certain metrics.

To setup a metric, complete the follow steps.



1. Click Alerts on the side menu.
2. Click Add Alert at the top of the page.
3. Select Metric as the alert type.
4. Select the aggregation and the metric that you would like to be performed on.
5. Select the scope if applicable.
6. Set the metric and time requirements for the alert to trigger.
7.