vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Enable your IBM Cloud Monitoring instance for platform metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling).
* To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).







 Command options 

--enable
: (Optional) Enable the setting for your account.

--disable
: (Optional) Disable the setting for your account.

--status
: (Optional) Display whether the setting is enabled for your account.





 Example 

Enable platform metrics for your account.

ibmcloud cr platform-metrics --enable







 ibmcloud cr private-only 

Prevent image pulls or pushes over public network connections for your account for the registry region that you're targeting. You must specify one of the command options or the command fails with an error.

ibmcloud cr private-only --enable | --disable | --status



 Prerequisites 

To find out about the required permissions, see [Access roles for configuring Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_configure).





 Command options 

--enable
: (Optional) Prevent image pulls or pushes over public network connections for your account.

--disable
: (Optional) Reinstate image pulls or pushes over public network connections for your account.

--status
: (Optional) Check whether the use of public connections is prevented for image pushes or pulls in your account.





 Example 

Prevent image pulls or pushes over public network connections for your account.

ibmcloud cr private-only --enable







 ibmcloud cr quota 

Displays your current quotas for traffic and storage, and usage information against those quotas for the registry region that you're targeting.

ibmcloud cr quota



 Prerequisites
Kubernetes Metrics Server v0.3.6 v0.3.7 See the [Kubernetes Metrics Server release notes](https://github.com/kubernetes-sigs/metrics-server/releases/tag/v0.3.7). 







 Change log for worker node fix pack 1.15.12_1550, released 17 August 2020 

The following table shows the changes that are in the worker node fix pack 1.15.12_1550. Worker node patch updates can be applied by updating, reloading (in classic infrastructure), or replacing (in VPC infrastructure) the worker node.



Changes since version 1.15.12_1549

 Component Previous Current Description 

 Ubuntu 18.04 packages N/A N/A Updated worker node image with package updates for [CVE-2020-11936](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11936), [CVE-2020-12400](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12400), [CVE-2020-12401](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12401), [CVE-2020-15701](https://nvd.nist.gov/vuln/detail/CVE-2020-15701), [CVE-2020-15702](https://nvd.nist.gov/vuln/detail/CVE-2020-15702), [CVE-2020-15709](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15709), and [CVE-2020-6829](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-6829).
For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).
* <TARGET_ID> is the ID of the target.



For example, you can run the following cURL request to get information about a target with the ID 00000000-0000-0000-0000-000000000000:

curl -X GET https://private.us-south.metrics-router.cloud.ibm.com/api/v3/targets/00000000-0000-0000-0000-000000000000 -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"





 Listing all targets using the API 

You can use the following cURL command to view all targets:

curl -X GET <ENDPOINT>/api/v3/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"

Where



* <ENDPOINT> is the API endpoint in the region where you plan to configure or manage a target. For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).



For example, you can run the following cURL request to get information about the targets that are defined in Dallas:

curl -X GET https://private.us-south.metrics-router.cloud.ibm.com/api/v3/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"





 HTTP response codes 

When you use the IBM Cloud Metrics Routing REST API, you can get standard HTTP response codes to indicate whether a method completed successfully.



* A 200 response always indicates success.
* A 4xx response indicates a failure.
* A 5xx response indicates an internal system error.



See the following table for some HTTP response codes:



Table 2. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful.
If you use a community Kubernetes cluster, you might also have the Red Hat OpenShift version of kubectl, which does not work with community Kubernetes clusters.

To check your client kubectl version against the cluster server version, run kubectl version --short.

 How to fix it 

[Install the version of the CLI](https://cloud.ibm.com/docs/containers?topic=containers-cli-install) that matches the version of your cluster.

If you have multiple clusters at different versions or different container platforms such as Red Hat OpenShift, download each kubectl version binary file to a separate directory. Then, you can set up an alias in your local command-line interface (CLI) profile to point to the kubectl binary file directory that matches the kubectl version of the cluster that you want to work with, or you might be able to use a tool such as brew switch kubernetes-cli <major.minor>.





 kubectl commands time out 

 What’s happening 

If you run commands such as kubectl exec, kubectl attach, kubectl proxy, kubectl port-forward, or kubectl logs, you see the following message.

<workerIP>:10250: getsockopt: connection timed out

kubectl -n kube-system logs metrics-server-65fc69c6b7-f682d -c metrics-server
Error from server: Get “https://10.38.193.213:10250/containerLogs/kube-system/metrics-server-65fc69c6b7-f682d/metrics-server”: EOF

kubectl -n kube-system exec -it metrics-server-65fc69c6b7-f682d -c metrics-server -- sh
Error from server: error dialing backend: EOF

 How to fix it 

Review and complete the following the steps for your cluster version.

Kubernetes version 1.21 and later
For more information, see [Enforcing private endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints-enforce-private).



* The route name must be 1000 characters or less and cannot include any special characters other than space, dash -, dot ., underscore _, and colon :.

The name must not include any personal identifying information (PII).



After you configure a route, it might take up to 1 hour for the configuration to be enabled.





 IAM Access 

Ensure you have the [correct IAM permissions to configure IBM Cloud Metrics Routing.](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-iam)





 IAM permissions 

The following table lists the IAM actions, their scope and the roles required to manage routes.



Table 1. IAM action scopes and roles for managing routes

 Task IAM Action IAM Policy scope IAM Roles 

 Create a route metrics-router.route.create Account Administrator <br>Editor 
 List all routes metrics-router.route.list Account Administrator <br>Editor <br>Operator <br>Viewer 
 Get details of a route metrics-router.route.read Account Administrator <br>Editor <br>Operator <br>Viewer 
 Modify a route metrics-router.route.update Account Administrator <br>Editor 
 Delete a route metrics-router.route.delete Account Administrator <br>Editor 







 Auditing events 

The following table lists the IAM actions, their scope and the roles required to manage routes.



Table 2. Activity Tracker auditing event actions

 Task Activity Tracker auditing event action 

 Create a route metrics-router.route.create 
 List all routes metrics-router.route.list 
 Get details of a route metrics-router.route.read 
 Modify a route metrics-router.route.update 
 Delete a route metrics-router.route.delete 







 CLI prerequisites
Rule 0: [551957a7-c1e3-4160-84d8-4268709f6743(mon-std)], ]]
Created At: 2023-05-30T08:04:53.183Z
Updated At: 2023-05-30T08:53:22.824Z







 Listing all routes in a region 

Use this command to list the configured routes for an IBM Cloud Metrics Routing region.

ibmcloud metrics-router route ls [--output FORMAT]



 Command options 

--output FORMAT
: Currently supported format is JSON. If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

help | --help | -h
: List options available for the command.





 Example 

The following is an example using the ibmcloud metrics-router route ls command.

ibmcloud mr route ls
OK
Routes
Name: route-all
ID: f22e9cb6-2fcd-456d-9cf2-27813b1cc375
CRN: crn:v1:bluemix:public:metrics-router:global:a/xxxx::route:f22e9cb6-2fcd-456d-9cf2-27813b1cc375
Rule 0: [551957a7-c1e3-4160-84d8-4268709f6743(mon-std)], ]]
Created At: 2023-05-30T08:04:53.183Z
Updated At: 2023-05-30T08:53:22.824Z







 API routes and actions 

The following table lists the actions that you can run to manage routes:



Table 1. route actions by using the IBM Cloud Metrics Routing REST API

 Action REST API Method API_URL 

 Create a route POST <ENDPOINT>/api/v3/routes
When the authorization that is allowed in a monitoring instance is set to IAM_ONLY, you get the following response {"errors":[{"reason":"Not enough privileges to complete the action","message":"Access is denied"}]} when you try to get the Monitor API token .



 Sample JSON code 

You can use the following sample JSON code to get the Monitor API token :

def get_sysdig_api_token(self, instance_guid):
""" Get the Monitor API token by calling the /api/token endpoint """
if self.access_token == None:
self.get_iam_token()
if self.access_token == None:
 If the token is still None we have problems ....
return None
headers = { "Authorization": self.access_token,
"Accept": "application/json",
"IBMInstanceID": instance_guid }
url = self.sysdig_endpoint + "/api/token"
response = requests.get(url, headers=headers)
if response.status_code == 200:
data = response.json()
return data["token"]
else:
print_error("Error getting Monitor API token - {}".format(response.text))
return None
Show more
Working with Monitor API tokens 

You can use Monitor API tokens to authenticate with the IBM Cloud Monitoring service when you use Python scripts or the IBM Cloud Monitoring REST API to automate routine tasks and monitor notifications.

Consider the following information for each instance of the IBM Cloud Monitoring service:



* There is a Monitor API token per team.
* If the token is compromised or your organization's security policies require resetting the token after certain conditions, a user with administration permissions can reset the API token.





 Getting the Monitor API token through the monitoring UI 

Complete the following steps to get the Monitor API token :



1. From the Selector button in the navigation bar, choose Settings
2. From the Monitor API section, copy the Monitor API Token.



After you get the token, you can run API calls and use this token in the Authorization header.

When you copy the token include the Bearer keyword: Authorization: Bearer MONITOR_API_TOKEN





 Resetting the Monitor API token through the monitoring UI 

Complete the following steps to reset the Monitor API token :



1. From the Selector button in the navigation bar, choose Settings.
2. In the Monitor API section, click Reset Token to reset the API token.







 Getting the Monitor API token by using the API 

You can use the Token API to get the Monitor API token .

For example, you can use the following cURL command to get the Monitor API token :

curl -X GET <MONITORING_REST_API_ENDPOINT>/api/token -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "TeamID: $TEAM_ID" -H "content-type: application/json"

GET <MONITORING_REST_API_ENDPOINT>/api/token -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "TeamID: $TEAM_ID" -H "content-type: application/json"

Where



* <MONITORING_REST_API_ENDPOINT> indicates the endpoint targetted by the REST API call.
[Create a custom bucket](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/mon-tut-2-custom-bucket.png)





 Step 3: Name the new bucket 

Give the bucket a memorable name. In this case the new bucket will be called monitored-files and it's being created in the us-east region.

![Name the bucket](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/mon-tut-3-name-bucket.png)





 Step 4: Add Monitoring 

Scroll down to the Monitoring and activity tracking section and toggle the radio button to Enable metrics monitoring. Select an appropriate plan, and give the new instance a memorable name. In this case, we're creating the instance in the same region as the bucket (us-east) so we'll name the instance US East MM so that we can easily find it later.

Enable monitoring for both usage and request metrics.

![Add AT](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/mon-tut-4-add.png)





 Step 5: Find the new instance of Monitoring 

Navigate back to the dashboard, and look for the new instance. Click on it to open the Monitoring console.

![Find AT](https://cloud.ibm.com/docs-content/v1/content/63322f2f3a72050206eb05ba7f590fdcb741105c/cloud-object-storage/images/mon-tut-5-find.png)
curl -X GET <MONITORING_REST_API_ENDPOINT>/api/token -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "TeamID: $TEAM_ID" -H "content-type: application/json"

GET <MONITORING_REST_API_ENDPOINT>/api/token -H "Authorization: $AUTH_TOKEN" -H "IBMInstanceID: $GUID" -H "TeamID: $TEAM_ID" -H "content-type: application/json"

Where



* <MONITORING_REST_API_ENDPOINT> indicates the endpoint targetted by the REST API call. For more information, see [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.

TeamID defines the team for which you want to get the Monitor API token .

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).



When the authorization that is allowed in a monitoring instance is set to IAM_ONLY, you get the following response {"errors":[{"reason":"Not enough privileges to complete the action","message":"Access is denied"}]} when you try to get the Monitor API token .



 Sample JSON code 

You can use the following sample JSON code to get the Monitor API token :

def get_sysdig_api_token(self, instance_guid):
""" Get the Monitor API token by calling the /api/token endpoint """
if self.access_token == None:
self.get_iam_token()
For example, if 10 MB/s of message traffic is produced by applications in the source service instance to the mirrored topics, an extra 10 MB/s of outgoing bandwidth is required to mirror these messages into the target instance. This must be allowed for alongside any existing outgoing bandwidth that is already used by consuming applications. The monitoring dashboards can be used to determine the network usage in a service instance. For more information, see [Monitoring Event Streams metrics](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metrics).





 Geographical location 

As with any networking, the maximum achievable throughput is a factor of the distance over which the data is transmitted (due to the increasing latency and packet loss). This affects the maximum throughput that can be achieved between the source and target instances. Place the target service instances in as geographically close location as possible to the source.

The following table provides guidance for the achievable throughputs:



Table 1. Throughput guidance

 Regions Max per-partition throughput Max total throughput 

 us-south <-> us-east 1.5 MB/s 35 MB/s 
 eu-gb <-> eu-de 2.5 MB/s 35 MB/s 
 au-syd <-> jp-tok 0.4 MB/s 12 MB/s 
 within same region eu-gb <-> eu-gb 2.5 MB/s 35 MB/s 



The numbers indicate:



* Max total throughput: The maximum total MB/s that can be mirrored across all selected topics.
* Max per-partition throughput: The maximum MB/s that can be mirrored within a single partition. Select the number of partitions that are configured for the source topics to ensure the per partition load remains within this limit.



Exceeding the limits results in an increasing time lag between the data in the source and target instances. Having a large data lag can result in significant data loss. The monitoring dashboards can be used to determine the latency for each topic.
SAP system monitoring is available through the [SAP Host Agent](https://help.sap.com/viewer/3ce0859db2164fe19541dda577d29020/7.5.9/en-US/48c6f9627a004da5e10000000a421937.html), which provides monitoring functions that are similar to on-premises installations.



 Monitoring for IBM Cloud Intel Virtual Servers (Gen2), on VPC Infrastructure 

The operating system metrics that the SAP Host Agent provides require the use of [IBM Cloud Metrics Collector for SAP](https://cloud.ibm.com/docs/sap?topic=sap-ibm-metrics-collector-for-sap-linux) and the correct SAP Host Agent patch level.





 Monitoring for IBM Power Virtual Servers 

For Infrastructure as a Service (IaaS) environments such as IBM Power Virtual Servers, the operating system metrics that the SAP Host Agent provides were enhanced. Make sure you have the prerequisite SAP Host Agent patch level installed. For a description of the new metrics and required SAP Host Agent patch level, see [SAP Note 2932766 - SAP on IBM Power Virtual Servers: Key Monitoring Metrics](https://launchpad.support.sap.com//notes/2932766).







 Support from IBM Cloud or SAP 

For full information regarding support from IBM Cloud or SAP, please read [Getting help and support from IBM Cloud or SAP](https://cloud.ibm.com/docs/sap?topic=sap-help-support).
Global attributes.

 Attribute Attribute name Attribute 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, a data center, or global. 
 Resource group ibm_resource_group_name The resource group where the service instance was created. 
 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 preceding reference. See the individual metrics for segmentation options.



Table 5. More attributes.

 Attribute Attribute name Attribute description 

 Service instance ibm_service_instance The service instance segment identifies the instance that the metric is associated with. 
 Service instance name ibm_service_instance_name The service instance name provides the user-provided name of the service instance that isn't necessarily a unique value, depending on the name provided by the user. 









 Next Steps 

You can manage the data that the Monitoring instance collects for you. From management to setting alerts, you can [get started ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://cloud.ibm.com/docs/Monitoring-with-Sysdig?topic=Monitoring-with-Sysdig-getting-started) monitoring your data quickly and efficiently.
The following table lists integration services that are enabled for IBM Cloud Monitoring:



Table 4. List of integration services

 Service CRN service name Metrics 

 [Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-getting_started) messagehub [Platform metrics](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-metrics) 
 [IBM MQ on Cloud](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-getting_started) mqcloud [Platform metrics](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-monitor_sysdig) 







 Networking services 

The following table lists services that are enabled for IBM Cloud Monitoring:



Table 5. List of networking services

 Service CRN service name Metrics 

 [IBM Cloud® DNS Services](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-getting-started) dns-svcs [Platform metrics](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-monitor-ibm-cloud-pm) 







 IBM Cloud platform services 



Table 6. IBM Cloud platform services that send metrics to IBM Cloud Metrics Routing

 Service CRN service name Metrics 

 [IBM Cloud Activity Tracker Event Routing](https://cloud.ibm.com/docs/atracker) atracker 
 [IBM Cloud Metrics Routing](https://cloud.ibm.com/docs/metrics-router) metrics-router 







 Security services 



Table 7. List of security services

 Service CRN service name More info
* To monitor management events, you must configure a bucket and specify the Activity Tracker instance where those events will be available for monitoring.
* To monitor data events, you must select the option Track data events when you associate a bucket with an Activity Tracker instance.









 Web and mobile services 

America

Asia Pacific

Europe



Table 13. Web and mobile services integration in America locations

 Service Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao) 

 Mobile Foundation ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 







 VPC infrastructure services 

America

Asia Pacific

Europe



Table 14. VPC events in America's locations

 Service Dallas (us-south) Washington (us-east) Toronto (ca-tor) Sao Paulo (br-sao) 

 Storage resources ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) !