vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Table 9. VMware

 Service CRN service name Metrics 

 [VMware as a Service](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-getting-started) vmware [Platform metrics](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-single-tenant-monitoring) 
 [VMware solutions](https://cloud.ibm.com/docs/vmwaresolutions) vmware-solutions [Platform metrics](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared-monitor) 







 VPC 



Table 10. List of VPC services (generation 2)

 Service CRN service name Metrics 

 [VPC virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers&interface=ui) is [Platform metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-monitoring-metrics) 
 [Flow Logs for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-flow-logs) is [Platform metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-fl-monitoring-metrics) 
 [Load Balancer for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-network-load-balancers) is.load-balancer [Application Load Balancer platform metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-monitoring-metrics-alb) <br>[Network Load Balancer platform metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb_monitoring-metrics)
Metric name ibm_is_vpn_gateway_bytes_out 
 Metric type gauge 
 Value type byte 
 Segment by Service instance, Service instance name, VPN name, IBM IS 







 VPN gateway total packets input 

Packets received per minute for a VPN gateway



Table 3: VPN gateway total packets input

 Metadata Description 

 Metric name ibm_is_vpn_gateway_packets_in 
 Metric type gauge 
 Value type none 
 Segment by Service instance, Service instance name, VPN name, IBM IS 







 VPN gateway total packets output 

Packets sent per minute for a VPN gateway



Table 4: VPN gateway total packets output

 Metadata Description 

 Metric name ibm_is_vpn_gateway_packets_out 
 Metric type gauge 
 Value type none 
 Segment by Service instance, Service instance name, VPN name, IBM IS 







 VPN gateway status 

Status for a VPN gateway (for example, 1=available, 0=unavailable)



Table 5: VPN gateway status

 Metadata Description 

 Metric name ibm_is_vpn_gateway_status 
 Metric type gauge 
 Value type none 
 Segment by Service instance, Service instance name, VPN name, IBM IS 







 VPN connection bytes input 

Bytes received per minute for a VPN gateway's connection



Table 6: VPN connection bytes input

 Metadata Description 

 Metric name ibm_is_vpn_connection_bytes_in 
 Metric type gauge 
 Value type byte 
 Segment by Service instance, VPN name, Connection name, Connection ID, IBM IS 







 VPN connection bytes output 

Bytes sent per minute for a VPN gateway connection



Table 7: VPN connection bytes output

 Metadata Description 

 Metric name ibm_is_vpn_connection_bytes_out 
 Metric type gauge 
 Value type byte 
 Segment by Service instance, VPN name, Connection name, Connection ID, IBM IS 







 VPN connection packets input 

Packets received per minute for a VPN gateway connection



Table 8: VPN connection packets input

 Metadata Description 

 Metric name ibm_is_vpn_connection_packets_in 
 Metric type gauge 
 Value type none
You do not need additional instrumentation or configuration in your hosts to obtain metrics that are collected automatically by the agent to gain insight into what is happening in them.

To monitor your infrastructure, network, and applications with the IBM Cloud® Monitoring service, you can deploy Monitoring agents on supported hosts. The host determines the agent type that you can deploy. The agent type determines the metrics that are collected automatically for that host.

To start collecting default metrics, you must configure a Monitoring agent per environment that you want to monitor.

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.



In addition, the Monitoring agent automatically collects the following types of metrics per Kubernetes or Red Hat OpenShift cluster:



* State metrics: Kube state metrics report on the health and state of the various objects that run inside Kubernetes components, such as deployments, nodes and pods. To see the list of metrics that are collected by default, see Kubernetes 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.
Monitoring flow logs for VPC metrics 

Use IBM Cloud® Monitoring to gain operational visibility into the performance and health of your applications, services, and platforms. It offers administrators, DevOps teams, and developers full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards.



 Platform metrics overview 

You can view platform metrics when you enable IBM Cloud Monitoring on your IBM Cloud platform. A 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 in mind:



* You can configure only one instance of the IBM Cloud Monitoring service per region to collect platform metrics.
* Platform metrics are regional. Metrics are monitored only from IBM Cloud Monitoring services, which are in the same region of the instance that you want to monitor.
* Metrics are collected automatically and are available for monitoring through the IBM Cloud Monitoring-enabled instance.





 Metric: Flow log bytes sent 

The number of bytes sent to Cloud Object Storage from a flow log collector.



Table 1: Flow log bytes sent

 Metadata Description 

 Metric name ibm_is_flow_logs_cos_sent_byte 
 Metric type gauge 
 Value type byte 
 Segment by IBM IS Generation 2, flow log collector virtual server attachment 









 Attributes for segmentation 



 Global attributes 

The following attributes are available for segmenting the previously listed metric.



Table 2: Global attributes

 Attribute Attribute Name Attribute Description 

 Cloud type ibm_ctype Type of IBM Cloud. Cloud type values are public, dedicated, or local. 
 Location ibm_location Location of the monitored resource. This value can be a region, data center, or global. 
 Resource ibm_resource Resource being measured by the service. Typically, this value is an identifying name or GUID. 
 Resource type ibm_resource_type Type of resource measured by the service. 
 Scope ibm_scope Scope of the account, organization, or space GUID that is associated with this metric.
* 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.



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





 getMappingHitsMetrics 

Returns the total number of hits at a certain frequency over a given range of time, per domain mapping. Frequency can be day, week, and month, where each interval is one plot point for a graph. Return data is ordered based on startDate, endDate, and frequency. 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.
* week - Weekly metrics data from startDate to endDate.
* month - Monthly metrics data from startDate to endDate.





* Return - A collection of objects of type SoftLayer_Container_Network_CdnMarketplace_Metrics



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





 getMappingHitsByTypeMetrics 

Returns the total number of hits at a certain frequency over a given range of time. Frequency can be day, week, and month, where each interval is one plot point for a graph. Return data must be ordered based on startDate, endDate, and frequency. The value of frequency is aggregate by default.



* Parameters:
See the [Prometheus metrics](https://sysdig.com/blog/prometheus-metrics/) for details.

Use an existing Monitoring instance or create a new instance as shown below:



1. Leave Use private endpoint checked if possible and click Create and connect.
2. Select a region where you have your cluster created.
3. Select Graduated Tier as your plan.
4. Create a unique Service name such as <your-initials>-monitoring.
5. Use the resource group associated with your cluster.
6. Leave IBM platform metrics to Disable and click Create.





 Monitor your cluster 

To check the health and performance of your app and cluster you can review the default (out-of-the-box) and/or custom application generated metrics that are captured.

Note: Change the interval to 10 M on the bottom bar of the UI.



1. Go back to the application running at http://$MYINGRESSSUBDOMAIN/ and click on the Monitoring tab, generate several metrics.
2. Back to the Monitoring UI, select Dashboards.
3. Search for the predefined dashboard named Workload Status & Performance.
4. In this dashboard, set the workload filter to app-log-analysis-deployment to focus on the metrics generated by the application deployed earlier.
5. Scroll through the dashboard to discover all the predefined graphs like HTTP Requests Count per Workload or HTTP Requests Latency per Workload, Resource usage by Pod.



The sample application that was deployed includes code to generate custom metrics. These custom metrics are provided using a Prometheus client and mock multiple access to API endpoints.

Zoom

![Dashboard showing API counter metrics](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution12/wolam_api_counter_total.png)

Figure 2. Dashboard showing API counter metrics



1.
To see your Db2 on Cloud customer metrics dashboards in Monitoring:



1. From the IBM Cloud navigation menu, select Observability.
2. Select Monitoring.
3. Select View IBM Cloud Monitoring to open the dashboard.



For more information, see [Monitoring Getting started tutorial](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started).





 Metrics available by Service Plan 



 Metric Name 

 [Database Availability Check](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_db_availability_check) 
 [Database commits time](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_db_commits_time) 
 [Database rollbacks](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_db_rollbacks) 
 [Disaster recovery Log Gap](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_dr_log_gap) 
 [High Availability Disaster Recovery Log Gap](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_hadr_log_gap) 
 [Is disaster recovery connected?](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_is_dr_connected) 
 [Last backup duration in minutes](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_last_backup_duration_minutes) 
 [Log Disk wait](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-monitoribm_db2_log_disk_wait)
- include: haproxy.backend.
- exclude: haproxy.
- exclude: metricC.



* You are configuring the monitoring agent to collect all data from metrics that start with metricA, metricB, and haproxy.backend.
* You are filtering out metrics that start with metricC and other metrics that start with haproxy.
* The entry exclude: metricA. is ignored.







 Changing the log level 

To configure the log level, you must customize the log section in the dragent.yaml file.

The monitoring agent generates log entries in /opt/draios/logs/draios.log.



* The log file rotates when it reaches 10MB in size.
* The 10 most recent log files are kept. The date-stamp that is appended to the filename is used to determine which files to keep.
* Valid log levels are: none, error, warning, info, debug, trace
* The default log level is info, where an entry is created for each aggregated metrics transmission to the backend servers, once per second, in addition to entries for any warnings and errors.
* You can customize the type of log and the entries that are collected by configuring the monitoring agent configuration file /opt/draios/etc/dragent.yaml. After you edit the file, you must restart the agent at the shell with service dragent restart to activate the changes.





Table 2. Log section entries

 Use cases Log section entry 

 Troubleshoot agent behavior file_priority: debug 
 Reduce container console output console_priority: warning 
 Filtering events by severity event_priority: warning 
 Verify what metrics are included or excluded metrics_excess_log: true
5 Default targets <br>Define 1 default target for each account to configure where metrics that are not explicitly managed in the account's routing rules are routed.<br><br>Consider defining a second default target for each account when you want to collect the data in a backup location or account. [link](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-planningplanning-4) 
 6 Number and location of targets <br>Define the targets where you plan to collect metrics based on your regulatory and corporate requirements. <br>Define service to service authorizations between the IBM Cloud Metrics Routing service and the IBM Cloud Monitoring instances that you configured as your destination targets. [link](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-planningplanning-5) 
 7 Routing rules <br>Define the routing rules that indicate how to route metrics in your acccount.<br><br>Decide if you want to drop the collection of metrics in 1 or more regions. Check any compliance requirements to confirm that you can. [link](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-planningplanning-6) 





 Locations and services 

Check the regions where you operate and identify how you can manage those metrics in the account:



* Identify the locations where you can configure IBM Cloud Activity Tracker to manage metrics. Check [Locations](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions).
* Identify which services in those locations generate metrics that you can route through IBM Cloud Metrics Routing. Check [Services generating metrics](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-cloud-services-mr).



You can use IBM Cloud Metrics Routing to manage metrics at the account-level.
The displayed metrics contain a timestamp in UNIX epoch time and the metric value for the time intervals that end at that timestamp. You can specify different scopes, and the time interval over which to report the metrics.

You can also specify the time interval over which to report your metrics. The following time intervals that are supported in the IBM Cloud Monitoring dashboard:



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









 Enabling metrics monitoring 

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

To receive monitoring metrics, use the following steps:



1. Navigate to the [metrics monitoring portal](https://cloud.ibm.com/observe/monitoring) and click Options > Create.
2. Select a region for your IBM Cloud Monitoring instance.

If you do not have an existing VPN gateway, see [Creating a VPN gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-the-ibm-cloud-consolevpn-ui) to provision one.

The region needs to match the location of your existing VPN gateway.
3. Choose your pricing plan.

Pricing plan details are explained in the selection window. Select the plan that best meets your requirements.
4. Provide a unique service name for your instance. The name can be any name that you want. The name has no impact on functionality.

Do not give multiple IBM Cloud Monitoring instances the same name.
5. Optionally, select a resource group. A resource group organizes account resources in customizable groupings. Any account resource that is managed by using IBM Cloud Identity and Access Management (IAM) access control belongs to a resource group within your account.

If you do not have any pre-configured resource groups, or have no reason to share this resource selectively, use the default selection.

If your account has multiple resource groups, you can choose which group has access to this IBM Cloud Monitoring instance.
Adding metrics to your service 

With IBM Cloud® Partner Center, you can measure various metrics for services with usage-based pricing plans. You can measure metrics on created instances and submit those measures to the metering service. The rating service aggregates the submitted usage into different buckets (instance, resource group, and account) based on the model that you choose. The aggregation and rating models for all the metrics in a plan are contained in the metering and rating definition documents for the plan. For more information, see [Metering integration](https://cloud.ibm.com/docs/sell?topic=sell-service-metering-integration).

To onboard your service to IBM Cloud, you are required to add metrics to your usage-based pricing plan to determine how customers are charged. When you add metrics to your pricing plan in Partner Center, you must request an initial approval. After your metrics are approved, you can test the pricing and usage from a customer's perspective and provide evidence from your testing to get the final approval for your pricing plan.



 Before you begin 

Before you can add metrics to your pricing plan, you must complete the following tasks:



1. [Submit tax and Electronic Funds Transfer documentation](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infosubmit-tax-eft)
2. [Export the Control Classification Number (ECCN)](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infoservice-eccn)
3. [Enter the United Nations Standard Products and Services Code (UNSPSC)](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infoservice-unspsc)
4. [Add a paid pricing plan](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infoadd-plan-paid)
5. [Confirm the digital platform reseller agreement](https://cloud.ibm.com/docs/sell?topic=sell-service-pricing-infodra)
* A metric for reporting the total number of members in a pool.
* A second metric for reporting the total number of healthy (or active) members in a pool.



: For more information on these new metrics or the IBM Cloud Monitoring service, refer to [Monitoring Application Load Balancer for VPC metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-monitoring-metrics-alb).





 09 August 2022 

VPC Instance Metadata service
: A restriction was removed from the [instance metadata service](https://cloud.ibm.com/docs/vpc?topic=vpc-imd-about&interface=ui) in which you had to stop and restart the virtual server instance to fully enable the metadata service. You can now create instances with the metadata service disabled and then enable the service for the instance to start using it immediately.





 08 August 2022 

Virtual servers for VPC
: You can now use the UI, CLI, and API to specify user tags for volume resources when you create an instance. You can add user tags to the instance's boot volume by editing the boot volume. You can also add user tags when attaching a data volume to the instance. For more information, see [Adding user tags to block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about&interface=uistorage-about-user-tags).

Snapshot and Backup for VPC
: The [quota of snapshots and backup snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasblock-storage-quotas) you can create per volume has been increased to 750. For more information about how these quotas are applied, see [Considerations when creating snapshots](https://cloud.ibm.com/docs/vpc?topic=vpc-snapshots-vpc-aboutsnapshots_vpc_considerations).





 01 August 2022 

Sharing images across an enterprise account (beta)
Metric Name ibm_databases_for_mysql_tuples_returned_rate 
 Metric Type gauge 
 Value Type rate 
 Segment By Service instance 







 Tuples updated count 

Tuples updated count



Table 32: Tuples updated count metric metadata

 Metadata Description 

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







 Tuples updated rate 

Tuples updated rate



Table 33: Tuples updated rate metric metadata

 Metadata Description 

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







 Used CPU for an instance 

How much CPU is used as a percentage of total CPU available. Only for deployments that have dedicated CPU.



Table 34: Used CPU for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_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 35: Used disk space for an instance metric metadata

 Metadata Description 

 Metric Name ibm_databases_for_mysql_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 36: Used memory for an instance metric metadata

 Metadata Description 

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







 WAL logs used bytes 

How much wal log file uses, in bytes



Table 37: WAL logs used bytes metric metadata

 Metadata Description 

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









 Attributes for Segmentation 



 Global Attributes 

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



Table 38: Global Attributes Metadata

 Attribute Attribute Name Attribute Description