vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* UI
* API







 Monitoring VPN servers 

IBM Cloud® Monitoring collects basic VPN server metrics on IBM Cloud for VPC, such as VPN server health status, VPN server active client count, VPN server authentication failure count, VPN server CRL days until expiration, and VPN server bytes input/output. These metrics are stored in IBM Cloud Monitoring. You can access metrics through the prebuilt dashboard.



 Platform metrics overview 

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

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



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







 Metrics available by service plan 

Metrics available by plan names are as follows:



* [VPN server data bytes input](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-monitoringibm_is_vpn_server_data_received_bytes)
* [VPN server data bytes output](https://cloud.ibm.com/docs/vpc?topic=vpc-vpn-client-to-site-monitoringibm_is_vpn_server_data_sent_bytes)
<br> <br>For more information, see [Retrieving an access token](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-access-token). 
 instance_ID Required. The unique identifier that is assigned to your Key Protect service instance. <br> <br>For more information, see [Retrieving an instance ID](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID). 



A successful request returns an HTTP 204 No Content response, which
indicates that the metrics policy was updated for your service
instance.

Optional: Verify that the metrics policy was updated by browsing the policies that are available for your Key Protect instance.

 {: codeblock}
$ curl -X GET 
"https://<region>.kms.cloud.ibm.com/api/v2/instance/policies?policy=metrics" 
  -H "accept: application/vnd.ibm.kms.policy+json" 
  -H "authorization: Bearer <IAM_token>" 
  -H "bluemix-instance: <instance_ID>"








 What's next 



* To find out more about configuring your Key Protect instance with Monitoring, check out [Monitoring Operational Metrics](https://cloud.ibm.com/docs/key-protect?topic=key-protect-operational-metrics).
* Configure a Prometheus server through a Kubernetes ConfigMap For more information, see [Collecting metrics from a Kubernetes cluster by using Prometheus remote write](https://cloud.ibm.com/docs/monitoring?topic=monitoring-prometheus_remote_write).







 Managing metrics 

By default, when you configure your Prometheus server to remote write to a Monitoring instance, all metrics are sent. These metrics are sent and include a remote_write: true label to easily identify them.



 Controling the metrics that are sent 

You can manage and control the metrics that you collect and send to a Monitoring instance. To select which series and labels to collect, and reduce the number of active series that are sent to the Monitoring instance, you can set up relabel configurations by using the write_relabel_configs block within your remote_write section.

For example, to collect metrics from 1 namespace my-namespace, you can add the following:

remote_write:
- url: https://<INGESTION_URL>/prometheus/remote/write
authorization:
credentials_file: /etc/secrets/<SECRET_NAME>
write_relabel_configs:
- action: keep
regex: my-namespace
source_labels:
- namespace





 Labeling metrics by Prometheus server 

You can specify custom labels that are sent along with each time series that is collected by a Prometheus server by using the external_labels block within global.

You can use these labels to filter and define the scope of the metrics that you monitor through dashboards in the Monitoring UI.

For example, if you have 2 different Prometheus servers configured to remote write to a Monitoring instance, you can include an external label to identify each server:

 Prometheus server 1
global:
external_labels:
provider: prometheus1
remote_write:
- url: ...

 Prometheus server 2
global:
external_labels:
provider: prometheus2
remote_write:
(https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-regions)

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

service_instance, resource_type, and resource
: Values appropriate to an [IBM Cloud service that generates metrics managed through [IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-cloud-services-mr)

Note these limitations when configuring inclusion filters.



* You can configure up to 7 inclusion filters for each rule.
* You can configure up to 20 values for inclusion_filter.values.
* Each value configured for inclusion_filter.values can be a maximum of 100 characters.







 IAM Access 

Users must have the appropriate IAM roles to work with routing rules. For information on IAM roles, see [Managing IAM access.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-iam)





 Defining routing rules by using the CLI 

Rules for routes and inclusion filters are defined in JSON format. Rules are defined in the following ways:



* By using the --rules option information is passed as JSON directly on the command.
* By using the --files option information is passed as a JSON file.





 Example that uses the --rules option 

The following example specifies rules directly on the --rules option. In this example, all metrics from us-east are routed to 11111111-1111-1111-1111-1111111111111.
* ns1.softlayer.com
* ns2.softlayer.com







 Which IP addresses are used for my secondary domain zone transfers? 

Transfers for your secondary domains come from one of the following four IP addresses:



* 66.228.118.67
* 67.228.119.235
* 208.43.119.235
* 12.96.161.249







 What is the difference between the public and private name servers? 

Our public name servers act as authoritative name servers for domain names that reside in our DNS servers and are managed through the [IBM Cloud console](https://cloud.ibm.com/). These servers answer and resolve domain names to your IP address for the general internet population.

Our resolving name servers are located on the private network and act as DNS resolvers for your server. The private resolvers query the internet's root name servers for domain lookups. For example, sending mail from your server requires an NSlookup of the destination domain name. The private DNS servers resolve this information over the private network to keep your bandwidth usage down, reduce the load on the authoritative servers, and offer quick resolution. Private network resolvers are a convenience service for our customers.





 What are my name server options? 

With a bare metal server there are four typical options for name servers:



* Use your domain name registrar's name servers to manage your domain names.
* Use IBM Cloud name servers to manage your domain names.
* Use a third-party DNS service to manage your domain names.
* Run your own name servers on your server to manage your domain names.



For the first three options, you will use name servers of the third party (for example, ns1.softlayer.com and ns2.softlayer.com). The last option uses your domain as the name server (for example, ns1.yourdomain.com and ns2.yourdomain.com), and it requires you to run DNS services on your server. You must also register your domain as a name server with your registrar. Name server registration is usually free, but it requires an additional step beyond the basic domain name registration process.
Working with the Linux agent 

After you provision an instance of the IBM Cloud Monitoring service in the IBM Cloud, you can deploy the Monitoring agent on your Linux hosts to collect data and metrics automatically. You can configure which metrics to monitor in each environment.

You can associate one or more tags to each monitoring agent. Tags are comma-separated values that are formatted as TAG_NAME:TAG_VALUE. When you monitor your environment, you can use these tags to identify metrics that are available from an agent. For example, you can include information about the service name and location with all of the metrics that are collected by this agent.



 Prereqs 

Check the topic [Tuning Sysdig Agent](https://docs.sysdig.com/en/docs/installation/sysdig-agent/troubleshooting-agent-installation/tuning-sysdig-agent/)





 Deploying the Linux agent by using a script 

Complete the following steps to configure a monitoring agent on Linux to collect and forward metrics to an instance of the IBM Cloud Monitoring service:



1. [Obtain the access key](https://cloud.ibm.com/docs/monitoring?topic=monitoring-access_keyaccess_key_ibm_cloud_ui).
2. Obtain the public or private ingestion URL. For more information, see [collector endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_ingestion).
3. Install the kernel headers.

When you install a monitoring agent, the agent uses kernel header files. [Learn more](https://docs.sysdig.com/en/agent-install--non-orchestrated.html)

Choose a distribution and run the following command for that distribution.

For Debian and Ubuntu Linux distributions, run the following command:

apt-get -y install linux-headers-$(uname -r)

For RHEL, CentOS, and Fedora Linux distributions, run the following command:

yum -y install kernel-devel-$(uname -r)
* You can define targets within the account or in a different account.



For more information, see [Targets](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-target).





 Routing rules in the account 

Define the routing rules that indicate how to route metrics in your account.



* Routes are global.
* You can define up to 4 routes per account.
* You can define 1 or more routes to configure how metrics across all regions in your account are collected and stored in 1 or more targets.
* For each route that you define, you can configure 4 rules. These rules are applied top down. When a rule is identified for a region, any follow up rules withing that route definition that apply to that region are not considered.



Decide if you want to drop the collection of metrics in 1 or more regions. Check any compliance requirements to confirm that you can.

-To drop the collection of metrics in 1 or more regions, you can configure a route for those regions with no targets defined.

For more information, see [Routes](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-routes).
Monitoring Cloud Foundry metrics 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

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. IBM Cloud Monitoring is operated by IBM Cloud Monitoring in partnership with IBM.



 Enabling platform metrics 

Platform metrics are metrics that are exposed by IBM Cloud Monitoring enabled resources in IBM Cloud. You must configure an IBM Cloud Monitoring instance in a region to monitor these metrics.

You can configure only 1 instance of the IBM Cloud Monitoring service per region to collect platform metrics.



* To configure the IBM Cloud Monitoring instance, you must set the platform metrics configuration setting. [Learn more](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling).
* If an IBM Cloud Monitoring instance in a region is already enabled to collect platform metrics, metrics from Monitoring-enabled resources are collected automatically and available for monitoring through this instance. For more information about Monitoring-enabled services, see [Cloud services](https://cloud.ibm.com/docs/monitoring?topic=monitoring-cloud_services).



To monitor Cloud Foundry apps, check that the IBM Cloud Monitoring instance is provisioned in the same region where your apps are running.





 Navigating to the monitoring UI 

To monitor Cloud Foundry apps, you must launch the monitoring UI in the region where your Cloud Foundry apps are running.

Complete the following steps to launch the monitoring UI from the Observability page and open the pre-defined Cloud Foundry dashboard:



1.
Monitoring Integration 

Monitoring for IBM Cloud® Messages for RabbitMQ deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward select information so you can monitor deployment health and resource usage. To see your Messages for RabbitMQ dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/4dfeb7bbbdd817dfbdb17402735fb55d9cfbc7fb/messages-for-rabbitmq/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.



 Monitoring Availability 

IBM Cloud Monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.

If you have deployments that are in Single-zone Region (SZR) che01 then your logs are forwarded to an IBM Cloud Monitoring instance in another region. You need to provision IBM Cloud Monitoring instances in the region where your metrics are forwarded to. Metrics for deployments in che01 go to jp-tok.





 Available Metrics 



Table 1: Available Metrics Reference Table

 Metric Name
Configuring the CLI to manage the IBM Cloud Metrics Routing account configuration 

You must configure your local IBM Cloud Metrics Routing CLI so that you can manage the IBM Cloud Metrics Routing account configuration by using CLI commands.

Complete the following steps to install the IBM Cloud Metrics Routing CLI:



1.  [Install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).
2.  Get the versions that are available for the metrics-router CLI plug-in. Run the following command:

ibmcloud plugin repo-plugins

For example, to get the versions of the IBM Cloud Metrics Routing CLI plug-in, run the following command:

ibmcloud plugin repo-plugins | grep metrics-router

The output of the command lists the versions that are available.
3.  Install the CLI plugin in your local system. Run the following command:

ibmcloud plugin install metrics-router [-v VERSION]

Where VERSION is the value of a listed version that is available for the plug-in.



If you have the IBM Cloud Metrics Routing CLI plug-in in your local system and you want to update the version of the plug-in, run the following command: ibmcloud plugin update metrics-router.

If you want to delete the IBM Cloud Metrics Routing CLI plug-in from your local system, run the following command: ibmcloud plugin delete metrics-router.
<metric category="config" context="host" device-id="" last-refresh="1607451781" refresh-interval="0" type="string" unit="none">
<name>Virtualization Solution</name>
<value>KVM</value>
</metric>
.
.
.
</metrics>



You might experience a delay before your data is available.





 Troubleshooting 

Use the following troubleshooting tips for IMCS.



 Uninstalling the Metrics Collector 



1. Run the following command to uninstall IMCS if you have any issues during the installation process. Then, reinstall it.

.uninstall-metric-collector.ps1

Are you sure you want to uninstall Metric Collector for SAP? (Default is No)
( y / n ) : y
Continuing uninstalling metric collector...
Removed scheduled task: IBM Metric Collector for SAP Updator
Successfully Uninstalled Metric Collector







 No metrics reported when you open the link 

No reported metrics is often due to the port not assigned to SAP Metrics Collector. It needs port 18181 available for localhost. If you have any other applications using the port, you must close the applications/owning process.



1. Use the following command to see whether the port is assigned to another application.

Get-NetTCPConnection -State listen

Zoom

![Figure 1. Ports that are used by applications](https://cloud.ibm.com/docs-content/v1/content/f89cc64b006ca59b35404693959c83d5747fee3e/sap//images/quickstudy-intel-vs-gen2-win-PS-Listen.png)

Figure 1. Ports that are used by applications









 Additional information 

If you don't have an IBM Cloud API key, the IMCS can't collect all of the metrics that are required by SAP, which include
Configuring account settings 

You can configure your account settings for IBM Cloud® Metrics Routing by using the IBM Cloud Metrics Routing CLI, the IBM Cloud Metrics Routing REST API, and Terraform scripts. Set these settings to define where and how metrics are collected, routed, and managed in your account.

When you configure or modify the IBM Cloud Metrics Routing account settings, consider the following information:



* Every time you modify the IBM Cloud Metrics Routing account settings, the data that is passed in the new request replaces any existing configuration data. You must ensure that any existing data is not deleted when you run an update of the account settings by including it in the new request.
* Before you disable public endpoints by setting --private-api-endpoint-only TRUE, make sure your account has access to the private endpoint. You can do this by running the command ibmcloud account show. If VRF Enabled is true and Service Endpoint Enabled is true then you have access to the private endpoint. If you do not have access to the private endpoint, you will be unable to re-enable the public endpoint since private endpoint access is required to re-enable the public endpoint.
* You can use private and public endpoints to manage settings. For more information about the list of ENDPOINTS that are available, see [Endpoints](https://cloud.ibm.com/docs/metrics_router?topic=metrics_router-endpoints).

Through the private network, you must use an API endpoint with the following format: https://private.<region>.metrics_router.cloud.ibm.com

Through the public network, you must use an API endpoint with the following format: https://<region>.metrics_router.cloud.ibm.com





 What data can you configure through the IBM Cloud® Metrics Routing account settings? 

You can define any of the following information:



* The location in your IBM Cloud account where the IBM Cloud Metrics Routing account configuration metadata is stored.

By metadata, we refer to the target/route/settings data that is available across the account in any region.
Maintain IBM Cloud high availability SLA Operate the Continuous Delivery service in accordance with the IBM Cloud Public [Service Level Agreements (SLAs)](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-slas). 
 Provide high availability capabilities Provide capabilities, such as IBM-owned infrastructure in multizone regions (MZR), to meet local access and low latency requirements for each supported region. Use the list of [available regions](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpoints) to plan for and create new instances of the service. 
 Monitor monitoring agents Provide images and instructions for how to install monitoring agents in environments that you want to monitor, such as Kubernetes, Linux, and Red Hat OpenShift. Install and configure monitoring agents. <br>Monitor that the agents are running in your environment, for example, by using monitoring alerts. 
 Deliver platform metrics Deliver platform metrics for Monitoring-enabled services to the monitoring instance that collects platform metrics and is located in the region where the platform metrics are generated. Configure 1 monitoring instance per region to collect platform metrics in that region. 







 Change management 

You and IBM share responsibilities for keeping IBM Cloud Monitoring service components at the latest version. You are responsible for change management of your monitoring agents, dashboards, and alert definitions.



Table 2. Responsibilities for change management

 Task IBM Responsibilities Your Responsibilities 

 Update the IBM Cloud Monitoring service Provide regular updates to the service with new features, fixes for defects, and security fixes. 
 Update the monitoring agent image that is hosted in IBM Cloud Provide regular updates to the monitoring agent image with new features, fixes to defects, and security fixes. Document changes in the [Agent release notes](https://docs.sysdig.com/en/sysdig-agent-release-notes.html) Update the agent to keep it up to date as new versions are made available. 
 Update default dashboards Update the default dashboards as requirements change. Update custom dashboards and track changes by using your own change management process. 
 Update pre-defined alert definitions Update the default alert definitions as requirements change.