vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To illustrate this, let's assume that your load balancer has two different listener protocols one HTTP on port 80 and another for TCP on port 8080. The dashboard would contain different lines showing 10 users who are connected through HTTP on Port 80 in one color, and 6 users connected through TCP on port 8080 in another color.



 Global attributes 

The following attributes are available for segmenting all three of the IBM Cloud Monitoring metrics.



Table 4: IBM Cloud Monitoring global attributes

 Attribute Attribute Name Attribute Description 

 Resource ibm_resource A load balancer's unique ID 
 Scope ibm_scope The account that is associated with a given load balancer 
 Service name ibm_service_name ibm-cloud-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 5: IBM Cloud Monitoring additional attributes

 Attribute Attribute Name Attribute Description 

 IBM Cloud Load Balancer appliance metrics ibm_cloud_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 Cloud Load Balancer listener metrics ibm_cloud_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 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 protocols include:



* HTTP
* HTTPS
* TCP



Specifying a listener port filters the metric by that listener. For example, if you don't specify a port, and the metric is Throughput, then IBM Cloud Monitoring reports the total throughput for all listener protocols. However, if the listener protocol is HTTP on port 80, then IBM Cloud Monitoring reports the throughput for HTTP traffic only.

You can also specify the time interval over which to report your metrics.
The v4 UUID or alias of the key that you want to delete. To retrieve a list of your available keys, run the [kp keys](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-keys) command.







 Optional parameters 



* --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.









 kp key show 

Retrieve details about a key, such as the key metadata and key material.

If the key was designated as a root key, the system cannot return the key material for that key.

ibmcloud kp key show KEY_ID_OR_ALIAS
-i, --instance-id INSTANCE_ID
[--key-ring KEY_RING_ID]
[-o, --output OUTPUT]



 Examples 

These are examples of kp key show.



 Example 1 

Create a root key and show the details.

 create a root key
$ ibmcloud kp key create my-root-key

Creating key: 'my-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
8635b804-9966-4918-a16b-d561fdbf181f my-root-key

 show key details
$ ibmcloud kp key show 8635b804-9966-4918-a16b-d561fdbf181f

Grabbing info for key id: 8635b804-9966-4918-a16b-d561fdbf181f...
OK
Key ID Key Name Description Creation Date Expiration Date
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/action-menu-icon.svg) to open a list of options for the key.
6. From the options menu, click Delete key, enter the key name to confirm the key to be deleted, and click Delete key.



After you delete a key, the key moves to the Destroyed state. You can [restore the deleted key](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-restore-keys) within 30 days after its deletion. Metadata that is associated with the key, such as the key's deletion date, is kept in the Hyper Protect Crypto Services database.





 Deleting keys with the API 

By default, Hyper Protect Crypto Services requires one authorization to delete a key. You can delete a key and the contents by making a DELETE call to the following endpoint.

https://api.<region>.hs-crypto.cloud.ibm.com:<port>/api/v2/keys/<key_ID>

This action can't succeed if the key is actively protecting one or more cloud resources. You can [review the resources](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-protected-resources) that are associated with the key, or [use the force parameter](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-keysdelete-key-force) at query time to delete the key.



1. [Retrieve your service and authentication credentials to work with keys in the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-kms-api).
2. Retrieve the ID of the key that you would like to delete.
* UI
* API







 Deleting keys using a single authorization 

You can use IBM® Key Protect for IBM Cloud® to delete an encryption key and its key material, if you are a manager for your Key Protect instance.

Before deleting keys, make sure to review the [Considerations before deleting and purging a key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-purge-keysdelete-purge-keys-considerations).



 Deleting keys in the console 

By default, Key Protect requires one authorization to delete a key. If you prefer to delete your encryption keys by using a graphical interface, you can use the IBM Cloud console.

[After you create or import your existing keys into the service](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-root-keys), complete the following steps to delete a key:



1. [Log in to the IBM Cloud console](https://cloud.ibm.com/login/).
2. Go to Menu > Resource List to view a list of your resources.
3. From your IBM Cloud resource list, select your provisioned instance of Key Protect.
4. On the application details page, use the Keys table to browse the keys in your service.
5. Click the ⋯ icon to open a list of options for the key that you want to delete.
6. From the options menu, click Delete key and confirm the key deletion in the next screen by ensuring the key has no associated resources. Note that you will not be able to delete the key if it is protecting a registered IBM Cloud resource that's non-erasable due to a [retention policy](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutableimmutable-terminology-policy).



After you delete a key, the key transitions to the Destroyed state. Any data encrypted by keys in this state is no longer accessible.
If a key is disabled, and then re-enabled quickly, requests made to that bucket may be rejected for up to an hour before cached key information is refreshed.





 Deleting keys and cryptographic erasure 

It isn't possible to delete a root key associated with a bucket that has a [retention policy](https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-immutable) in place. The bucket must be first emptied and destroyed before the root key can be deleted. For more information, [see the Key Protect documentation](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-purge-keysdelete-purge-keys-considerations).

Cryptographic erasure (or crypto-shredding) is a method of rendering encrypted data unreadable by [deleting the encryption keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-security-and-compliancedata-deletion) rather than the data itself. When a [root key is deleted in Key Protect](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keys), it will affect all objects in any buckets created using that root key, effectively "shredding" the data and preventing any further reading or writing to the buckets. This process is not instantaneous, but occurs within approximatedly 90 seconds after the key is deleted.

Although objects in a crypto-shredded bucket can not be read, and new object can not be written, existing objects will continue to consume storage until they are deleted by a user.





 Restoring a deleted key 

As an admin, you might need to [restore a root key that you imported](https://cloud.ibm.com/docs/key-protect?topic=key-protect-restore-keys) to Key Protect so that you can access data that the key previously protected. When you restore a key, you move the key from the Destroyed to the Active key state, and you restore access to any data that was previously encrypted with the key.
* KEY_ID_OR_ALIAS

The v4 UUID or alias of the key that you want to delete. To retrieve a list of your available keys, run the [kp keys](https://cloud.ibm.com/docs/key-protect-cli-plugin?topic=key-protect-cli-plugin-key-protect-cli-referencekp-keys) command.









 kp key create 

[Create a root key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-create-root-keys) in the Key Protect instance that you specify or [import your own key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-import-root-keys)

Root keys must be 16, 24, or 32 bytes long; corresponding to 128, 192, or 256 bits.

ibmcloud kp key create KEY_NAME
-i, --instance-id INSTANCE_ID
[--key-ring KEY_RING_ID]
[-k, --key-material KEY_MATERIAL]
[-n, --encrypted-nonce NONCE]
[-o, --output OUTPUT]
[-s, --standard-key]
[-v, --iv IV]



 Examples 

These are examples of kp key create.



 Example 1 

Create a root key.

 create a root key
$ ibmcloud kp key create my-root-key

Creating key: 'my-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
24203f96-b134-440e-981a-a24f2d432256 my-root-key





 Example 2 

Create a root key and show the JSON output.

 create a root key
$ ibmcloud kp key create my-root-key --output json

{
For a detailed description of the request, see the Key Protect [REST API reference doc](https://cloud.ibm.com/apidocs/key-protect).





 What's next 

To learn how to delete and purge a key using the UI, check out [Deleting keys using a single authorization](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keys). For information about how to do this using the API, click the API tab at the beginning of the topic.

To learn how to delete and purge a key that holds a dual-authorization deletion policy using the UI, check out [Deleting keys using dual authorization](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-dual-auth-keys). For information about how to do this using the API, click the API tab at the beginning of the topic.
You can [review the resources](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-protected-resources) that are associated with the key, or [use the force parameter](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-keysdelete-key-force) at query time to delete the key.



1. [Retrieve your service and authentication credentials to work with keys in the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-set-up-kms-api).
2. Retrieve the ID of the key that you would like to delete.

You can find the ID for a key in your service instance by [retrieving a list of your keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-keys), or by accessing the IBM Cloud console.
3. Run the following cURL command to permanently delete the key and the contents.

curl -X DELETE "https://api.<region>.hs-crypto.cloud.ibm.com:<port>/api/v2/keys/<key_ID>" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>" -H "x-kms-key-ring: <key_ring_ID>" -H "prefer: <return_preference>"

Replace the variables in the example request according to the following table.



Table 1. Describes the variables needed to delete keys with the API

 Variable Description 

 region Required. The region abbreviation, such as us-south or au-syd, that represents the geographic area where your Hyper Protect Crypto Services instance resides. For more information, see [Regional service endpoints](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-regionsservice-endpoints). 
 port Required. The port number of the API endpoint.
Delete key [Deleting keys in the console (single authorization)](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keysdelete-key-gui). [Deleting keys with the GUI (single authorization)](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-keysdelete-keys-gui). 
 [Deleting a key with dual authorization](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-dual-auth-keysdelete-dual-auth-keys-api). [Authorize deletion for a key with the GUI (dual authorization)](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-dual-auth-keysset-key-deletion-console). 
 Restore key [Restoring a deleted key with the console](https://cloud.ibm.com/docs/key-protect?topic=key-protect-restore-keysrestore-ui). [Restoring a deleted key with the GUI](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-restore-keysrestore-ui). 







 Manage root keys with the API 

You can use the API to disable, enable, delete, or restore your root keys. Table 6 describes each action and links to detailed steps for the Key Protect or Hyper Protect Crypto Services API. For more information about the relationship of user actions and key states, see [Root key states and user actions](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-managingbyok-root-key-states).

Because deleting a root key makes all resources that are protected by it unusable (status = unusable), program your applications to check the status of the resource (such as a volume, snapshot, or image) before it attempts to use it.
.catch(err => {
console.warn(err);
});







 Deleting an API key 

If you are using a key rotation strategy, you might want to delete an older key and replace it with a new key.

To delete an API key, complete the following steps:



1. In the IBM Cloud console, go to Manage > Access (IAM) > API keys.
2. Identify the row of the API key that you want to delete, and select Delete from the Actions![List of actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) menu.
3. Confirm the deletion by clicking Delete.



To delete an API key that is not your own, but you have access to manage, go to the API keys page. Then, select the All user IBM Cloud API keys option from the View menu to find the API key.





 Deleting an API key by using the CLI 

To delete an API key by using the CLI:

Enter ibmcloud iam api-key-delete NAME in your command prompt, specifying the name of the key to delete.





 Deleting an API key by using the API 

To delete an API key by using the API, call the [IAM Identity Service API](https://cloud.ibm.com/apidocs/iam-identity-token-apidelete-api-key) as shown in the following example:



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE 'https://iam.cloud.ibm.com/v1/apikeys/APIKEY_UNIQUE_ID' -H 'Authorization: Bearer TOKEN' -H 'Content-Type: application/json'

DeleteApiKeyOptions deleteApiKeyOptions = new DeleteApiKeyOptions.Builder()
.id(apikeyId)
If there are no associations after using Sync, the key can be deleted normally.

If the associations are still there after Sync:



* You can use the Key Protect API to [force deletion on the key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-keysdelete-keys-force-delete).
* You can delete the resources associated with the key, and then delete the key normally.







 Getting help and support 

If you have problems or questions when you are using Key Protect, you can check IBM Cloud, or get help by searching for information or by asking questions through a forum. You can also open a support ticket.

You can check whether IBM Cloud is available by going to the [status page](https://cloud.ibm.com/status?tags=platform,runtimes,services).

You can review the forums to see whether other users ran into the same problem. When you are using the forums to ask a question, tag your question so that it is seen by the IBM Cloud development teams.



* If you have technical questions about Key Protect, post your question on [Stack Overflow](https://stackoverflow.com/search?q=key-protect+ibm-cloud) and tag your question with "ibm-cloud" and "key-protect".
* For questions about the service and getting started instructions, use the [IBM developerWorks dW Answers](https://developer.ibm.com/answers/topics/key-protect/) forum. Include the "ibm-cloud" and "key-protect" tags.



See [Asking a question](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatarasking-a-question) for more details about using the forums.

For more information about opening an IBM support ticket, or about support levels and ticket severities, see [Contacting support](https://cloud.ibm.com/docs/get-support).
For a detailed description of the available parameters, see the Key Protect [REST API reference doc](https://cloud.ibm.com/apidocs/key-protect).







 Key purge 

When you delete a key, you immediately deactivate its key material and move it to a backstore in the Key Protect service. Four hours after a key is deleted, the key becomes available to be manually purged. Thirty days after a key is deleted, the key becomes non-restorable and the key material is destroyed. After a key has been deleted for 90 days, if not manually purged, the key becomes eligible to be automatically purged and all its associated data will be permanently removed, or "hard deleted", from the Key Protect service.

For more information about deleting and purging keys, check out [About deleting and purging keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-delete-purge-keys).

The following table lists which APIs you can use to retrieve data related to a deleted key.



Table 4. Lists the API that users can use to view details about a key and its registrations.

 API Description 

 [Get key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-key) Retrieve key details 
 [Get key metadata](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-key-metadata) Retrieve key metadata 
 [Get registrations](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resources) Retrieve a list of registrations associated with the key
Delete the key by clicking the X next to the key to be deleted.







 Viewing a service key by using the UI 

You must have the manager role for the IBM Log Analysis service to complete this step.

For more information, see [service roles](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-iamservice).

Complete the following steps to view a service key:



1. [Launch the IBM Log Analysis web UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-launch).
2. Click the Settings icon ![Settings icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/admin.png).
3. Select Organization.
4. Select API keys.

If you have the correct permissions, the available service keys are displayed in the Service Keys section.







 Rotating an service key through the UI 

If the service key is compromised or you have a policy to renew it after a number of days, you can generate a new key and delete the old one.

To renew the service key for an IBM Log Analysis instance by using the IBM Log Analysis Web UI, complete the following steps:



1. [Launch the IBM Log Analysis web UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step2).
2. Click the Settings icon ![Settings icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/admin.png) > Organization.
3. Select API keys.

You can see the service keys that are enabled.
4.
delete the root key
$ ibmcloud kp key delete $KEY_ID

Deleting key: 62ad0cd5-70a4-4c4d-9d87-5f4db620b120, from instance: a192d603-0b8d-452f-aac3-f9e1f95e7411...
OK
Deleted Key
62ad0cd5-70a4-4c4d-9d87-5f4db620b120

 list keys - verify the key was deleted
$ ibmcloud kp keys

Retrieving keys...
OK
Key ID Key Name

 restore the deleted key
$ ibmcloud kp key restore $KEY_ID -k $KEY_MATERIAL --output json

{
"id": "62ad0cd5-70a4-4c4d-9d87-5f4db620b120",
"name": "my-base64-root-key",
"type": "application/vnd.ibm.kms.key+json",
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:key:62ad0cd5-70a4-4c4d-9d87-5f4db620b120"
}

 list keys - verify the key was restored
$ ibmcloud kp keys

Retrieving keys...
OK
Key ID Key Name
62ad0cd5-70a4-4c4d-9d87-5f4db620b120 my-base64-root-key





 Example 2
* UI
* API







 Deleting keys by using a single authorization 

If you are a manager for your IBM Cloud® Hyper Protect Crypto Services instance, you can use Hyper Protect Crypto Services to delete root keys or standard keys and the contents.

Before you delete keys, make sure you understand [the concept of deleting and purging keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-purge-keys) and review the [considerations](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-purge-keysdelete-purge-keys-considerations).



 Deleting keys with the console 

By default, Hyper Protect Crypto Services requires one authorization to delete a key. If you prefer to delete your encryption keys by using a graphical interface, you can use the IBM Cloud console.

[After you create or import your existing keys into the service](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-create-root-keys), complete the following steps to delete a key:



1. [Log in to the IBM Cloud console](https://cloud.ibm.com/login).
2. Go to Menu > Resource list to view a list of your resources.
3. From your IBM Cloud resource list, select your provisioned instance of Hyper Protect Crypto Services.
4. On the KMS keys page, use the Keys table to browse the keys in your service.
5. Select the key that you want to delete and click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/action-menu-icon.svg) to open a list of options for the key.
6. From the options menu, click Delete key, enter the key name to confirm the key to be deleted, and click Delete key.
.catch(err => {
console.warn(err);
});







 Deleting an API key 

If you are using a key rotation strategy, you might want to delete an older key and replace it with a new key.

To delete an API key, complete the following steps:



1. In the IBM Cloud console, go to Manage > Access (IAM) > API keys.
2. Identify the row of the API key that you want to delete, and select Delete from the Actions![List of actions icon](https://cloud.ibm.com/docs-content/v1/content/814aeaf04800bb4f74ea1c057d4abb166a5f357a/icons/action-menu-icon.svg) menu.
3. Confirm the deletion by clicking Delete.



To delete an API key that is not your own, but you have access to manage, go to the API keys page. Then, select the All user IBM Cloud API keys option from the View menu to find the API key.





 Deleting an API key by using the CLI 

To delete an API key by using the CLI:

Enter ibmcloud iam api-key-delete NAME in your command prompt, specifying the name of the key to delete.





 Deleting an API key by using the API 

To delete an API key by using the API, call the [IAM Identity Service API](https://cloud.ibm.com/apidocs/iam-identity-token-apidelete-api-key) as shown in the following example:



* Curl
* Java
* Python
* Go
* Node



curl -X DELETE 'https://iam.cloud.ibm.com/v1/apikeys/APIKEY_UNIQUE_ID' -H 'Authorization: Bearer TOKEN' -H 'Content-Type: application/json'

DeleteApiKeyOptions deleteApiKeyOptions = new DeleteApiKeyOptions.Builder()
.id(apikeyId)