vania-janet/multiturn-rag-retrieval-data huggingface dataset:
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-provisioner: vpc.block.csi.ibm.io
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 10Gi
Access Modes: RWO
VolumeMode: Filesystem
Used By: my-pod-11a1a1a1a1-1a11a
Events: <none>
3. If the PVC is not mounted to a pod, review the steps for [setting up Block Storage for VPC](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-blockvpc-block-add) and mount the PVC to a pod. Then try to view the metrics again.
4. If the PVC is mounted, follow the steps for [manually verifying the Block Storage for VPC metrics](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_monitoringmanual-monitor-metrics) then [open a support issue](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helphelp-support). The steps for manual verification in the CLI allow you to view your metrics, but are not a solution for metrics that do not populate in the console. However, if you are able to manually verify your metrics, this indicates that there is a console issue for which you must open an issue.





 Manually viewing storage metrics in the CLI 

If your storage metrics are not visible in the monitoring dashboard, you can manually view them in the CLI. Note that manual verification of your storage metrics is a temporary workaround and not a permanent monitoring solution for viewing metrics. After completing the following steps, if you are able to manually view the metrics in the CLI and not the dashboard, this indicates that there is a console issue for which you must [open a support issue](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helphelp-support).
To resolve the issue, try debugging your [Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-ts-locations-debug) or [cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_clusters). 
 registered Satellite Config components are installed in the cluster, but no resources are currently watched. To set up Watch-keeper, see [Reviewing resources that are managed by Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-satcon-resources). 









 Setting up Monitoring for Satellite location platform metrics 

Forward and view additional metrics for Satellite in an IBM Cloud Monitoring instance that is enabled for platform-level metrics.

Metrics are available for the Satellite Link component of your location to help you monitor the performance of specific Link endpoints or of all Link endpoints for the location. For example, you can monitor the latency or throughput of a specific Link endpoint that you created.



1. Create or choose an existing Monitoring instance.



* If you already have a Monitoring instance in the same IBM Cloud region that your Satellite location is managed from, and the Monitoring instance is configured to collect platform metrics, the metrics that are generated for your Satellite location are automatically forwarded to this Monitoring instance.
* Otherwise, to set up Monitoring for your Satellite location:



1. [Provision an IBM Cloud Monitoring instance](https://cloud.ibm.com/catalog/services) in the same IBM Cloud region that your Satellite location is managed from.
2. [Enable the instance for platform-level metrics collection](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling). Note that within one region, only one Monitoring instance can be enabled for platform metrics collection.





2. In the Monitoring dashboard, click Open Dashboard for your Monitoring instance.
3. In the Monitoring dashboard, click Dashboards > IBM > Satellite Link - Overview. The pre-defined dashboard for Satellite Link metrics opens.
For more information, see [Offering comparison chart](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-inst_comp_chart).







 What is included in a vCenter Server instance? 

For more information, see [Technical specifications for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverviewvc_vcenterserveroverview-specs).





 What is included in a VMware vSphere instance? 

For more information, see [Technical specifications for VMware vSphere instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vs_vsphereclusteroverviewvs_vsphereclusteroverview-specs).





 Is a two node vCenter Server instance highly available? 

Deploy production workloads into environments that have at least three nodes.

The VMware vSphere DRS (Distributed Resource Scheduler) and VMware HA (High Availability) are enabled by default. However, VMware suggests that you place each of the three NSX Controllers on an individual node.

In the two-node minimum deployment, one node has one NSX Controller, and the other node has two NSX Controllers. If the node with two NSX Controllers goes down, NSX Controller operations are placed in read-only mode, and new VMs (virtual machines) or vMotion VMs might experience networking issues.

When a third node is added to a two-node cluster, vCenter Server automatically rebalances the three NSX Controllers across the three nodes and creates a highly available environment.





 Can I set up VMware vCenter HA configuration? 

You can configure vCenter HA, but configuration support is not provided by IBM Cloud for VMware Solutions.





 Can clusters be renamed? 

For a new vCenter Server instance, you can set the name of the initial cluster that is created during deployment.
For more information about how it works, see [Auto Scale for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-auto-scale-instance-groupauto-scale-vpc).





 What permissions do I need for using auto scale? 

You can check the required permissions for actions on instance templates, instance groups, instance group managers, memberships, and policies in the [Required permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls). For more information about using IBM Cloud Identity and Access Management (IAM) to assign users access, see [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).





 Can I set multiple scaling policies? 

You can set scaling policies for these metrics: CPU utilization (%), RAM utilization (%), Network in (Mbps), Network out (Mbps). You can define more than one target metric policy, but only one policy for each type of metric.





 Are there any limitations on network interfaces or floating IP addresses when I use auto scale? 

Instance groups do not support instance templates that have the following configurations:



* Secondary network interfaces are not supported. Only one, primary network interface for an instance template is supported in an instance group.
* A primary IP address or floating IP addresses assigned to the primary interface is not supported.







 Can I use custom metrics for auto scale? 

No. Currently custom metrics are not supported.





 How many IP addresses are available for instances? 

Currently 6 IP addresses in each subnet are allotted as overhead. The remaining IP addresses in the subnet are available to assign to instances that are provisioned in the instance group.

Ensure that you use a subnet size of 32 or greater. Using the same subnet for multiple instance groups can create capacity issues.





 How are instances balanced across subnets? 

Currently instances are provisioned at random to one of the instance group's subnets.
Using IBM Metrics Collector for SAP (IMCS) on Windows 

The IBM® Metrics Collector for SAP (IMCS) on Windows is a requirement by SAP Support for IBM Cloud® Virtual Private Cloud Infrastructure only when SAP workloads are running on the virtual server instance (VSI).



 Getting an IBM Cloud API key 

You need an IBM Cloud API key for IMCS to successfully collect all required metrics. The API key grants view access to IBM Cloud infrastructure services. You can install IMCS without an API key. However, some metrics are missing and the virtual server is not supported by SAP.

For a list of missing metrics, see [Additional Information](https://cloud.ibm.com/docs/sap?topic=sap-ibm-metrics-collector-for-sap-windowsaddl-info).

You need to create only one Service ID and one API Key per Account. You can use the same Service ID and API Key for all the Metric Collectors that are installed in the virtual server that is associated to the Account.



 Creating a Service ID 

You need to first create a Service ID and then the related API key. Use the following steps to create a Service ID.



1. Sign in to the [IBM Cloud console](https://cloud.ibm.com) and click Manage > Access (IAM).
2. Click Services IDs > Create.
3. Enter a Name and Description for the Service ID and click Create. You can assign the Access Policy after your Service ID is created.
4. Click Access Policies > Assign Access.
5. Click IAM Services for Assign Service ID additional access.
6. Select VPC Infrastructure service for What type of access do you want to assign?





1. Leave the default Account for in
2. Leave All resource types for Resource type and click Viewer for Platform Access.
3. Click Add > Assign. The VPC Infrastructure Service policy is assigned to your Service ID.







 Creating an API Key for the Service ID. 

Use the following steps to create an API Key for the new Service ID.



1. Select Service IDs and your newly created Service ID
In vCenter, you can use an extra set of vSAN Health Checks. Installation of the Management Pack for vSAN provides more dashboards to aid with the monitoring of vSAN.

VMware Aria Operations generates an alert if a problem occurs in the SDDC product components in the storage area network that the VMware vSAN adapter is monitoring. An alert that is related to configuration compliance and health is passed through VMware SDDC Health Solution management pack from VMware vSAN Management Pack. vSAN is monitored with the VMware Aria Operations vSAN Management Pack through the vCentre appliance by using a vSAN adapter. The default collection interval is five minutes and the vSAN adapter also collects Health Check Service and Performance Service metrics from vSphere objects. The Health Check Service interval is configured in the vSphere interface and is 60 minutes by default.

To ensure that the vSAN adapter can collect all performance data, the vSAN performance service must be enabled in vSphere.





 Monitoring of NSX for vSphere 

To monitor NSX, the following tools are implemented:



* VMware Aria Operations Manager
* VMware Aria Operations for Logs
* VMware Aria Operations for Networks



This enables system administrators to monitor, manage, and troubleshoot VMware NSX. The VMware Aria Operations Management Pack for VMware NSX provides visibility into the network topology. NSX dashboards provide a quick overview of the NSX environment and the health of its components. Correlation between NSX objects and vSphere objects enables easier troubleshooting.

VMware Aria Operations uses the management pack to poll VMware NSX for configuration, performance, and support data. On behalf of VMware Aria Operations, the Management Pack converts the polling requests into REST API calls to retrieve the required data from NSX Manager.

The NSX components need to be configured to send syslog to VMware Aria Operations for Logs.
You can install only one agent on a Kubernetes cluster on IBM Cloud Kubernetes Service. You can install additional agents on different clusters.

You cannot install more than one agent in a single Kubernetes cluster. You will get a failure with namespace conflict error.





 What type of Schematics jobs can I run in my Agent? 

You can run Schematics Workspace Terraform jobs on an Agent. You can also run Schematics Action jobs, Ansible playbooks on an Agent.





 How can I see the Schematics job results and logs, for the workloads running on an agent? 

The workspace job or action job logs are available in Schematics UI console. You can also access these job logs using the Schematics Workspace API, or CLI.





 How many Schematics jobs can run in parallel in the Agent? 

Currently, an agent can run three Schematics jobs in parallel. Any additional jobs are queued and will execute when prior jobs complete execution.

In future, you will be able to customize an agent to increase the number of job Pods, to increase the number of jobs that can run concurrently.





 What is the minimum cluster configuration required in Agent release? 

The agent needs IBM Cloud Kubernetes Service Service with minimum three worker nodes, with a flavor of b4x16 or higher.





 How many workspaces can be assigned to an agent? 

Currently, you can assign any number of workspaces to an agent. The workspace jobs are queued to run on the agent, based on the agent assignment policy. The agent periodically polls Schematics for jobs to run, with a polling interval of one minute. By default, the agent runs only three jobs in parallel. The remaining jobs are queued.





 How many jobs can run in parallel on an agent? 



* Schematics Agent can perform three Git download jobs in parallel.
* Schematics Agent can run three Workspace jobs (Terraform commands), in parallel.
* Schematics Agent can run three Action jobs (Ansible playbook), in parallel.







 What is the default polling interval for Agents? 

Schematics maintains a queue of jobs that will be executed on an agent.
--------------------



 Monitoring in IBM Cloud 

You can use IBM Cloud® Monitoring to monitor the performance and overall system health of your organization.

You can collect metrics from a number of platforms, orchestrators, and a wide range of applications such as Prometheus, JMX, StatsD, Kubernetes, and other application stacks, that are available in the IBM Cloud, outside the IBM Cloud, or on-prem. You can also add more metrics by creating custom metrics and adding integrations.

You can monitor metrics through the Monitoring web UI, or through other platforms like Grafana.

The following figure shows the components overview for the IBM Cloud Monitoring service that is running on IBM Cloud:

Zoom

![IBM Cloud Monitoring component overview on the IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring/images/overview.svg)

Figure 1. IBM Cloud Monitoring component overview on the IBM Cloud

When you configure a Monitoring agent, data for default metrics is automatically collected. These metrics include metadata that you can use to label, segment, and display metrics when you monitor them. 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.

You can monitor hosts in IBM Cloud, on-prem, and in other clouds.



Table 1. Get started working with IBM Cloud Monitoring

 Source Info
For more information about using IBM Cloud Identity and Access Management (IAM) to assign users access, see [Granting user permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resources).
* Can I set multiple scaling policies?

You can set scaling policies for these metrics: CPU utilization (%), RAM utilization (%), Network in (Mbps), Network out (Mbps). You can define more than one target metric policy, but only one policy for each type of metric.
* Are there any limitations on network interfaces or floating IP addresses when I use auto scale?

Instance groups do not support instance templates that have the following configurations:



* Secondary network interfaces are not supported. Only one, primary network interface for an instance template is supported in an instance group.
* A primary IP address or floating IP addresses assigned to the primary interface is not supported.



* Can I use custom metrics for auto scale?

No. Currently custom metrics are not supported.
* How many IP addresses are available for instances?

Currently 6 IP addresses in each subnet are allotted as overhead. The remaining IP addresses in the subnet are available to assign to instances that are provisioned in the instance group.

Ensure that you use a subnet size of 32 or greater. Using the same subnet for multiple instance groups can create capacity issues.
* How are instances balanced across subnets?

Currently instances are provisioned at random to one of the instance group's subnets.
* What happens when I update an instance template?

When the instance template that is used by an instance group is updated, all future instances that are created for the instance group use the new instance template. No changes are made to existing instances in the instance group.
* Can I update all instances in an instance group with a new instance template?

You can update all of the instances in an instance group by deleting the existing memberships and applying a new instance template.
Attribute Attribute Name Attribute Description 

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







 Additional attributes 

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



Table 4: Additional attributes

 Attribute Attribute Name Attribute Description 

 IBM Load Balancer for VPC appliance metrics ibm_is_load_balancer_appliance_ip The metrics coming from the load balancer back-end. Because the load balancer is highly available, multiple appliances support each load balancer for redundancy. 
 IBM Load Balancer for VPC listener metrics ibm_is_load_balancer_listener_port The metrics that are gathered from individual listeners and their ports. Configure the listeners in your load balancer settings. The monitoring metrics reflect the metrics coming from those listeners. 



The displayed metrics contain a timestamp in UNIX Epoch Time and the metric value for the time interval ending at that timestamp. You can specify different scopes, as well as the time interval over which to report the metrics.

The supported listener protocol for network load balancer is:



* TCP



You can also specify the time interval over which to report your metrics. Time intervals that are supported in the dashboard are:



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



The number of data points you can report is roughly the same for each time interval. For example, if the interval is 1 hour, then each data point represents 5 minutes of data. If the interval is 2 weeks, then each data point represents 24 hours of data.







 Enabling metrics monitoring 

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

To do so, follow these steps:



1. Navigate to the [metrics monitoring portal](https://cloud.ibm.com/observe/monitoring), then click Create a monitoring instance.
2.
Then, review [Headers for IAM Tokens](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curlmon-curl-headers-iam) and [Token headers](https://cloud.ibm.com/docs/monitoring?topic=monitoring-mon-curlmon-curl-headers-sysdig) before you retry the request.





 Are your dashboards, alerts, and scripts no longer returning what you intended? 

IBM Cloud Monitoring has changed its metrics store. This change has deprecated and changed a number of metrics and labels and has changed metric behavior. See [Enhanced metric store](https://cloud.ibm.com/docs/monitoring?topic=monitoring-metrics_store) for details on the new metric store.





 Where is the topology map? 

With the IBM Cloud Monitoring change the metrics store, the topology map has been deprecated. See [Enhanced metric store](https://cloud.ibm.com/docs/monitoring?topic=monitoring-metrics_store) for details on the new metric store.
Monitoring 

IBM Cloud® Monitoring is a cloud-native, and container-intelligence management system that you can include as part of your IBM Cloud architecture. Use it 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.



 Opting in to and enabling IBM Cloud® Data Engine metrics 

Before you can start to use Data Engine metrics, you must first opt in, and then enable platform metrics by completing the following steps.



1. Enable platform metrics for Data Engine. For more information, see [Enabling platform metrics](https://cloud.ibm.com/docs/Monitoring-with-Sysdig?topic=Monitoring-with-Sysdig-platform_metrics_enabling). The owner of the account has full access to the metrics data. For more information about managing access for other users, see [Getting started tutorial for IBM Cloud® Monitoring](https://cloud.ibm.com/docs/Monitoring-with-Sysdig?topic=Monitoring-with-Sysdig-getting-started).
2. To navigate from the Data Engine instance page to the IBM Cloud Monitoring dashboard, click the overflow menu (three vertical dots) of the instance page (Service instance options) and select Monitoring.

On your first usage, you might see a welcome wizard. To advance to the dashboard selection menu, select Next and then Skip on the Choosing an installation method page. Accept the prompts that follow. You can then select the Data Engine dashboard.

Dashboards are available only after metrics start to be recorded, which might take a few minutes to initialize.







 Data Engine metrics cost information 

Before you opt in to using IBM Cloud® Monitoring metrics, be aware of the cost of doing so. Every instance of Data Engine makes four metrics available, each time series has a monthly cost of $0.08, which leads to a monthly cost of $0.32 per instance.

For more information, see [IBM Cloud Monitoring pricing !