vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
4.4 stable true
4.2 deprecated false

The IBM Cloud Databases API deployables endpoint returns all deployable databases. Use the version parameter to return the version number.

GET /v5/ibm/deployables







 Minor versions
region_location = var.region
key_protect = data.ibm_kms_key.central_kms_root_key.id
storage_class = "smart"
}

You can find more examples in the GitHub repository [cross-account-resource-sharing](https://github.com/IBM-Cloud/cross-account-resource-sharing).





 Typical service-to-service authorizations 

A dependency on a key management service (KMS) like [Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-getting-started-tutorial) and [Hyper Protect Crypto Services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started) is typical for cloud-based solutions. A KMS instance holds the root keys for customer-managed encryption. Most services support customer-controlled encryption keys. Instead of cloud-object-storage (Object Storage) in the example above, many other services can use a KMS instance shared across accounts.

Other typical (target) services for service-to-service authorization and candidates for resource sharing include:



* [Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage): Several services require or are able to store data and log files in a storage bucket. This includes the archival of access logs and monitoring data. Other services like Data Engine need to access buckets to perform data analysis. And yet another category of services need access to subscribe to change notifications to trigger the execution of actions.
* [Event Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-getting-started): To push out information about events to subscribers, service instances need to access an Event Notifications instance.
* A blog post, for example: [Messages for RabbitMQ 3.8 End of Life in July 2022](https://www.ibm.com/cloud/blog/announcements/messages-for-rabbitmq-38-end-of-life-in-july-2022)
* An announcement in your service's Release Notes, for example: [IBM Cloud® Messages for RabbitMQ 3.8 End of Life in July 2022](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-rabbitmq-relnotesmessages-for-rabbitmq-25jan2022)
* A notification by email through the IBM Cloud Databases API. This email contains a Notifications link that takes you to a Notifications Management page. Make sure that these announcements are not being caught by your email service's spam filter. For more information, see [Setting up Distribution Lists for IBM Cloud Notifications](https://www.ibm.com/cloud/blog/announcements/setting-up-distribution-lists-for-ibm-cloud-notifications).



For more information, see [Programmatic Methods for Checking Version Status](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-versioning-policy-major-version-eol-check-version-status).



 Programmatic Methods for Checking Version Status 

The following [IBM Cloud Databases deployables command](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployables-show) shows deployable database types, specifically the available versions of databases, and their preferred or stable status.

ibmcloud cdb deployables-show [--stable] [--preferred] [--json]

Check the status of a major version by reviewing the output of the deployable command, specifically Status and Preferred. The following output example shows that version 4.4 is the Preferred version and version 4.2's Status is deprecated.

Database Type: mongodb
Version Status Preferred
4.4 stable true
The following are examples of how to use the logging Configuration API.

A category must exist before you create a view. In these examples, replace <MY_CATEGORY> with your category.

In these examples, <SERVICE_KEY> is the [service key](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_keys) for your IBM Log Analysis instance.



 Creating a view 

The following sample creates a view.

curl https://api.us-south.logging.cloud.ibm.com/v1/config/view 
-H 'content-type: application/json' 
-H 'servicekey: <SERVICE_KEY>' 
-d '{
"name": "My RC 200",
"query": "reasonCode:200",
"hosts": ["myHostName"],
"category": ["<MY_CATEGORY>"]
}'





 Creating a view and attaching an alert 

The following sample creates a view and associates an email alert with the view.

curl https://api.eu-de.logging.cloud.ibm.com/v1/config/view 
-H 'content-type: application/json' 
-H 'servicekey: <SERVICE_KEY>' 
-d '{
"name": "My RC 200",
"query": "reasonCode:200",
"hosts": ["myHostName"],
"category": ["TEST"],
"channels": [
{
"integration": "email",
"emails": "myemail@ibm.com"],
"triggerlimit": 15,
"triggerinterval": "5m",
"immediate": true,
"terminal": true,
"operator": "presence",
"timezone": "Europe/London"
}
]
}'
Show more





 Modifying a view by adding an alert 

The following modifies a view by adding an alert.
This is the body that you want to send to APNs server, this must be JSON in string format. For more information regarding APNs body, follow this documentation [here](https://developer.apple.com/library/archive/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/CreatingtheNotificationPayload.html).

For compatibility with an earlier version for existing Push notification customers, the previous unified data format is still supported but is deprecated.



 Example: Deprecated Push notification service compatible format: 

"ibmenapnsbody": "{"en_data":{"alert":"alert","url":"https","badge":9,"sound":"bingbong.aiff","payload":{"myaarray":["cc75e4a6-edd8-3bec-a7c3-dfca6572a03b"]},"type":"DEFAULT","subtitle":"dummy","title":"dummy1","body":"body","ios_action_key":"key","interactive_category":"interactiveCategory","title_loc_key":"titleLocKey","loc_key":"GAME_PLAY_REQUEST_FORMAT","launch_image":"image.png","title_loc_args":["Shelly","Rick"],"loc_args":["Shelly","Rick"],"attachment_url":"some url","apns_collapse_id":"12","apns_thread_id":"1","apns_group_summary_arg":"apnsGroupSummaryArg","apns_group_summary_arg_count":1}}"







 ibmenchromebody(string/json) 

This attribute is needed if you want to send push notification to a chrome device. This is the body that you want to send to web server, this must be JSON in string format.
Similarly, when you [create](https://cloud.ibm.com/apidocs/vpc/latestcreate-bare-metal-server) an s390x bare metal server, or [add](https://cloud.ibm.com/apidocs/vpc/latestcreate-bare-metal-server-network-interface) a network interface to an existing s390x bare metal server, you must specify an interface_type of hipersocket. For more information, see the [IBM HiperSockets Implementation Guide](https://www.redbooks.ibm.com/abstracts/sg246816.html).



s390x bare metal servers have different network bandwidth and maximum network interface limits from x86 bare metal servers.







 20 September 2022 



 For all version dates 

Deprecated VPN for VPC ciphers. The following VPN IKE and IPsec ciphers are now deprecated:



* Authentication algorithms md5 and sha1
* Encryption algorithm triple_des
* Diffie–Hellman groups 2 and 5



You have until 13 December 2022 to upgrade to more secure ciphers. After this date, VPN connections using deprecated ciphers will have a status of down (and no longer transfer data) until you upgrade from the weak cipher. For more information, see [Upgrading weak cipher suites on a VPN gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-upgrading-weak-ciphers).

Additional VPN for VPC ciphers. VPN gateways now provide new algorithms to help meet your security and compliance requirements.

[IKE policy](https://cloud.ibm.com/apidocs/vpc/latestlist-ike-policies) methods now support the sha384 value for the authentication_algorithm property, aes192 value for the encryption_algorithm property, and groups 15-18, 20-24, and 31 for the dh_group property.
* metrics-server
* olm-operator and catalog components (1.16 and later)
* vpn
* In gateway-enabled classic clusters, ibm-gateway-controller



Can I install other plug-ins or add-ons than the default components?
: Yes. IBM Cloud Kubernetes Service provides other plugin-ins and add-ons that you can choose from to add capabilities to your cluster. For example, you might want to [use Helm charts](https://cloud.ibm.com/docs/containers?topic=containers-helm) to install the [block storage plug-in](https://cloud.ibm.com/docs/containers?topic=containers-block_storageinstall_block) or [strongSwan VPN](https://cloud.ibm.com/docs/containers?topic=containers-vpnvpn-setup). Or you might want to enable IBM-managed add-ons in your cluster, such as [Istio](https://cloud.ibm.com/docs/containers?topic=containers-istio). You must update these Helm charts and add-ons separately by following the instructions in the Helm chart readme files or by following the steps to [update managed add-ons](https://cloud.ibm.com/docs/containers?topic=containers-managed-addonsupdating-managed-add-ons).



 Managing automatic updates for Fluentd 

When you create a logging configuration for a source in your cluster to forward to an external server, a Fluentd component is created in your cluster. To change your logging or filter configurations, the Fluentd component must be at the latest version. By default, automatic updates to the component are enabled.

As of 14 November 2019, a Fluentd component is created for your cluster only if you [create a logging configuration to forward logs to a syslog server](https://cloud.ibm.com/docs/containers?topic=containers-healthconfiguring). If no logging configurations for syslog exist in your cluster, the Fluentd component is removed automatically.
If specified, output is returned in JSON format. If JSON is not specified, output is returned in a tabular format.

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







 ibmcloud metrics-router target ls 

Use this command to list the configured targets for IBM Cloud Metrics Routing.

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



 Command options 

--output FORMAT
: Supported format is JSON. If specified, output is returned in JSON format. If JSON is not specified, output is returned in a tabular format.

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







 ibmcloud metrics-router setting get 

Use this command to get the settings for the IBM Cloud Metrics Routing account configurations.

ibmcloud metrics-router setting get [--output FORMAT]



 Command options 

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

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







 ibmcloud metrics-router setting update 

Use this command to modify current settings such as the default targets, permitted target regions, primary and secondary metadata regions in IBM Cloud Metrics Routing. Any value that is different from when the target was originally created is updated to the value specified in the command. If no options are specified, the current settings are returned.

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 cannot enable the public endpoint. Private endpoint access is required to enable the public endpoint.
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 

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







 ibmcloud cr quota-set 

Modify the specified quota for the registry region that you're targeting.

ibmcloud cr quota-set [--traffic TRAFFIC] [--storage STORAGE]



 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 

--traffic TRAFFIC
: (Optional) Changes your traffic quota to the specified value in megabytes.
Settings actions by using the IBM Cloud Metrics Routing REST API

 Action REST API Method API_URL 

 Get settings information GET <ENDPOINT>/api/v3/settings 
 Update settings PATCH <ENDPOINT>/api/v3/settings 



For more information about the REST API, see [the settings API](https://cloud.ibm.com/apidocs/metrics-router/metrics-router-v3get-settings).



 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 usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 3. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Metrics Routing processing.
For more information, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).

<route_ID>
: ID of the route.

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

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





 Listing all routes using the API 

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

curl -X GET <ENDPOINT>/api/v3/routes -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 route. 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 routes that are defined in Dallas:

curl -X GET https://private.us-south.metrics-router.cloud.ibm.com/api/v3/routes -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.
: Any location where [IBM Cloud Metrics Routing is available.](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)

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

--force
: Run the command without prompting for confirmation. This flag only applies when the resulting route discards platform metrics.

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







 ibmcloud metrics-router route rm 

Use this command to delete an IBM Cloud Metrics Routing route.

ibmcloud metrics-router route rm --route ROUTE [--force]



 Command options 

--route ROUTE
: The name or ID of the route to be deleted.

--force
: Deletes the route without providing the user with any additional prompt.

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







 ibmcloud metrics-router route get 

Use this command to get information about an IBM Cloud Metrics Routing route.

ibmcloud metrics-router route get --route ROUTE [--output FORMAT]



 Command options 

--route <ROUTE_ID>
: The name or ID of the route.

--output FORMAT
: If JSON is specified, output is returned in JSON format. If JSON is not specified, output is returned in a tabular format.
Example 

The following is an example using the ibmcloud metrics-router route update --route my-route --name my-new-route-name command.

ibmcloud mr route update --route target1 --name target2
OK
Route
Name: target2
ID: 06a29ca2-40f5-4371-ae3c-76a896577bd3
CRN: crn:v1:bluemix:public:metrics-router:global:a/xxxx::route:06a29ca2-40f5-4371-ae3c-76a896577bd3
Rule 0: [551957a7-c1e3-4160-84d8-4268709f6743(mon-std)], ]]
Created At: 2023-05-30T21:14:21.460Z
Updated At: 2023-05-30T21:19:40.953Z







 Deleting a route using the CLI 

Use this command to delete a route.

ibmcloud metrics-router ROUTE rm --route route [--force]



 Command options 

--route ROUTE
: The ID or name of the route.

--force | -f
: Will delete the route without providing the user with any additional prompt.

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





 Example 

The following is an example using the ibmcloud metrics-router route rm --route xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx command.

Are you sure you want to remove the route with route ID xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx? [y/N]>y
OK
Route with name xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx was successfully removed.







 Getting information about a route using the CLI 

Use this command to get information about a route for an IBM Cloud Metrics Routing region.
ID: 		000000000-00000000-0000-0000-00000000
REGION: us-east
CRN: 		crn:v1:bluemix:public:metrics-router:us-south:a/xxxxxxxxxx:000000000-00000000-0000-0000-00000000
Type: 		sysdig_monitor
Destination CRN: 		crn:v1:bluemix:public:sysdig-monitor:au-syd:a/xxxxxxxxxx:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx::
CreatedAt: 		2021-07-21T16:04:15.174Z
UpdatedAt: 		2021-07-21T16:04:15.174Z







 Listing all targets in a region 

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

ibmcloud metrics-router target 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 target ls command.

Name ID Region Type 	CreatedAt UpdatedAt
target-01 xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx us-south sysdig_monitor 2020-11-18T03:52:08.603Z 2020-11-19T03:52:08.603Z
target-02 yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy us-south sysdig_monitor 2020-11-18T03:52:01.592Z 2020-11-19T03:52:08.603Z
: 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)

--rules RULES
: A JSON formatted rule definition enclosed in single quotation marks. For example,

--rules '[{"action": "send", "targets":{"id": "11111111-1111-1111-1111-111111111111"}], "inclusion_filters":{"operand": "location","operator": "is","values":"us-south"]}]}]

Where target_ids is a comma-separated list of target IDs.

The rule definition can optionally also include inclusion filters. For example,

[{
"action": "send",
"targets": {
"id":"11111111-1111-1111-1111-111111111111"
}],
"inclusion_filters":
{
"operand": "service_name",
"operator": "in",
"values":
"appconnect",
"cloudant",
"containers-kubernetes"
]
},
{
"operand": "location",
"operator": "in",
"values":
"us-south",
"eu-de"
]
}
]
}]
Show more

Where:

action
: Action defines whether IBM Cloud® Metrics Routing includes or excludes metrics on the route.