vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Valid combinations and values for the "throughput" and "storage_size" are listed in the following table.



Table 2. Valid combinations and values for 'throughput' and 'storage_size'

 Throughput capacity (maximum) "throughput" value to specify Storage capacity "storage_size" value to specify 

 1 (150 MB/s) 150 2 TB 2048 
 4 TB 4096 
 6 TB 6144 
 8 TB 8192 
 10 TB 10240 
 12 TB 12288 
 2 (300 MB/s) 300 4 TB 4096 
 8 TB 8192 
 12 TB 12288 
 3 (450 MB/s) 450 6 TB 6144 
 12 TB 12288 







 Example 

Deploy a service instance configured with a base capacity unit:



* 150 MB/s of throughput capacity.
* 2 TB of storage capacity for data retention.



Scale this service instance to a configuration of a base capacity unit, one extra capacity unit, and 4 TB of extra storage to provide:



* 300 MB/s of throughput capacity.
* 8 TB of storage capacity for data retention.





1. If you don't already have one, create an Event Streams service instance.

a. Log in to the IBM Cloud console.

b. Click the Event Streams service in the Catalog.

c. Select the Enterprise plan on the service instance page.

d. Review capacity selections of 150 MB/s throughput and 2 TB storage.

e. Enter a name for your service instance. You can use the default value.

f. Click Create. (For information about the amount of time needed to create the service instance, see [Choosing your plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-choosing-your-planwhat-is-supported)).
2. Log in to the IBM Cloud CLI.

ibmcloud login
3. Get the resource name of your Event Streams service instance.

ibmcloud resource service-instances

(You can find the name of your instance in the Name column.)
4.
If an image that you're expecting to see doesn't show in the list that is produced, see [Why doesn't the retention command show all the images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-list-retention) for assistance.
4. Verify that the images were deleted by running the following command, and check that the images do not show in the list.

ibmcloud cr image-list

If listing images times out, see [Why is it timing out when I list images?](https://cloud.ibm.com/docs/Registry?topic=Registry-troubleshoot-image-timeout) for assistance.







 Set a retention policy for your namespaces 

You can set a retention policy for your namespaces to retain only images that meet your criteria. The retention policy runs automatically to clean up your namespaces.

You can choose whether to exclude untagged images from the clean-up process.

You can use the [ibmcloud cr retention-policy-set](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_retention_policy_set) command to set a policy that retains a specified number of images for each repository within a namespace in IBM Cloud Container Registry. All other images in the namespace are deleted and moved to the trash. When you set a policy it runs immediately, then it runs daily. You can set only one policy in each namespace.

Where an image, within a repository, is referenced by multiple tags, that image is counted only once. Newest images are retained. Age is determined by when the image was created, not when it was pushed to the registry.

If you delete an image in error, you can restore the image by using the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_trash_list) and [ibmcloud cr image-restore](https://cloud.ibm.com/docs/Registry?topic=Registry-containerregclibx_cr_image_restore) commands.
[Classic icon](https://cloud.ibm.com/docs-content/v1/content/921d024aca5ff45536208840a52f864567eb4068/icons/classic.svg).
3. Click Storage > Cloud Backup to display the backup services.
4. Select the instance name of the IBM Cloud Account.
5. Click View backup portal to start the portal in your browser.







 Step 4: Configuring the backup agent and the backup schedule 

After you ordered your IBM Cloud Backup for Classic and the agent is installed on the server, you can start creating backups of your data. Through the IBM Cloud Backup for Classic portal, you can manage and monitor your backups. You can choose between manual or automatic backup agent configuration methods.



* The automatic agent configuration creates a backup job of the complete C Drive (Windows® OS) or ./ <root> directory (Linux® OS) with Monthly and Daily Retention schemes.



This job can be modified after it was configured.



1. Create a password.
2. Confirm the password.
3. Add a password hint.
4. Click Configure automatically.





* If you choose to configure the IBM Cloud Backup for Classic agent manually, the automatic settings are ignored. Then, you can specify the folders and files to be kept with a retention scheme of your choice. For more information, see [Configuring simple file-level backup](https://cloud.ibm.com/docs/Backup?topic=Backup-configureFileBackup).



For more information about Retention Schemes, see the [FAQ](https://cloud.ibm.com/docs/Backup?topic=Backup-faqsfaqs).

Archiving is not supported. When you create a retention scheme or modify an existing scheme, make sure that the Archiving option is not selected.





 Step 5: Running your first backup job 



1. The new job is displayed on the Computers tab. To start the job, click Select Actions, and click Run Job.
2.
4.0.8 [6.2.0](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-release-notes-chat6.2.0) 







 28 June 2023 

IBM Watson® Assistant Cartridge for IBM Cloud Pak® for Data Version 4.7.0 is available
: Watson Assistant for IBM Cloud Pak® for Data 4.7.0 is compatible with IBM Cloud Pak® for Data Version 4.7. See the [support matrix](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-installinstall-support-matrix) for more details.

The new Watson Assistant experience is now available for all new instances
: When you create a new instance of Watson Assistant, the new Watson Assistant experience will be the default interface to use for building your assistants. The new experience makes it easier to use actions to build customer conversations. If you don't want to use the new experience, you can use the Manage menu to switch to the classic experience. For details, see [Welcome to the new Watson Assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-welcome-new-assistant).

All languages are now enabled by default
: You don't need to add languages during installation. All supported languages are now enabled by default with no increase in footprint. For details, see [Supported languages](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-language-support).

New algorithm version Latest (20 Dec 2022) provides improved irrelevance detection
: A new algorithm version is available. The Latest (20 Dec 2022) version includes a new irrelevance detection implementation to improve off-topic detection. For details, see [Algorithm version and training](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-algorithm-version).

Actions templates updated with new design and new choices
: The actions template catalog has a new design. Now you can select multiple templates at the same time.
In the UI, you can define custom views, dashboards, parsing templates, screens, and exclusion rules that you can use to view and analyze data.

To reuse resource definitions that you define in your auditing instance, you can export these resources from an IBM Cloud Activity Tracker instance as a JSON file. Then, you can import the definitions into other auditing instances. For example, you can reuse your resources across different environments for your stage, pre-production, and production instances. [Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-reuse_resource_definitions).

Backup resource definitions into a version control system such as a git repository where you can control access to the archived files and manage versions.





 Archive log data to a COS bucket 

Enable archiving of your data from an auditing instance to an IBM Cloud Object Storage (COS) bucket.

After you provision an auditing instance, you can configure archiving to an IBM Cloud Object Storage (COS) bucket. You can create different types of buckets based on your requirements.

When you plan the bucket for an auditing instance, consider the following information:



Table 5. COS bucket requirements

 Requirement Question to answer Information 

 Type of workload [1] How often do you need to access the data? [Information about storage classes](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-classesclasses-about) 
 Retention policy [2] Do you need to protect data from being deleted? [Information about Immutable Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-immutable) 
 Expiration policy [3] Do you need automatic deletion of files? [Information about expiration rules](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-expiry) 
 Long-term retention policy [4] Do you need to keep data for a long period of time?
After you add the response type and customize the transfer messages, select Salesforce from the Service desk routing field.
4. In the Button ID field, add the button_id value for the alternate routing destination that you want the assistant to use for conversations about only this topic. For example, 5733i0000008yGz.

Be sure to specify the exact right syntax for the button_id value. The value is not validated by the service as you add it to your dialog.



If the special routing that you apply fails to deliver the message for any reason, the routing preference that is specified in the Salesforce service desk setup page is used. If both routing preferences fail, the transferred message is treated like a new message in Salesforce. The standard Salesforce routing rules are followed.
To find out about the required permissions, see [Access roles for using Container Registry](https://cloud.ibm.com/docs/Registry?topic=Registry-iamaccess_roles_using).





 Example 

List the retention policies in your account.

ibmcloud cr retention-policy-list

For more information about how to use the ibmcloud cr retention-policy-list command, see [Retaining images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retention).







 ibmcloud cr retention-policy-set 

Set a policy to retain the specified number of images for each repository within a namespace in IBM Cloud Container Registry. All other images in the namespace are deleted. When you set a policy it runs interactively, then it runs daily. You can set only one policy in each namespace.

You can choose whether to exclude all untagged images from the total number of images that you decide to retain.

Where an image, within a repository, is referenced by multiple tags, that image is counted only once. Newest images are retained. Age is determined by when the image was created, not when it was pushed to the registry.

If a retention policy deletes an image that you want to keep, you can restore the image. To identify the image, list the contents of the trash by running the [ibmcloud cr trash-list](https://cloud.ibm.com/docs/cli?topic=cli-containerregclibx_cr_trash_list) command and restore the selected image by running the [ibmcloud cr image-restore](https://cloud.ibm.com/docs/cli?topic=cli-containerregclibx_cr_image_restore) command.

If you want to cancel a retention policy, see [Update a retention policy to keep all your images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_retentionretention_policy_keep).

ibmcloud cr retention-policy-set [--retain-untagged] --images IMAGECOUNT NAMESPACE



 Prerequisites
New beta en-WW_Medical_Telephony model is now available
: A new beta next-generation en-WW_Medical_Telephony is now available. The new model understands terms from the medical and pharmacological domains. Use the model in situations where you need to transcribe common medical terminology such as medicine names, product brands, medical procedures, illnesses, types of doctor, or COVID-19-related terminology. Common use cases include conversations between a patient and a medical provider (for example, a doctor, nurse, or pharmacist).

The new model is installed from the Speech services custom resource by setting enWwMedicalTelephony to enabled: true. The model is available for all supported English dialects: Australian, Indian, UK, and US.



* The model supports language model customization and grammars as beta functionality.
* It supports most of the same parameters as the en-US_Telephony model.
* It does not support the following parameters: low_latency, profanity_filter, redaction, and speaker_labels.
* At this time, it does not support smart_formatting for IBM Cloud Pak for Data.



For more information, see [The English medical telephony model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ngmodels-medical).

Update to Chinese zh-CN_Telephony model
: The next-generation Chinese model zh-CN_Telephony has been updated for improved speech recognition. The model continues to support low latency. By default, the service automatically uses the updated model for all speech recognition requests. For more information about all available next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng).

If you have custom language models that are based on the updated model, you must upgrade your existing custom models to take advantage of the updates by using the POST /v1/customizations/{customization_id}/upgrade_model method.
Provision an Event Streams service instance in your account and a service cluster in your Satellite location.
5. Configure block storage for your Satellite location that Event Streams then allocates during the service instance provision process. Event Streams uses the block storage for the retention of your message data.

The block storage capacity cannot be scaled up for the initial release of Satellite plan for Event Streams.

Event Streams stores three replicas of your message data to ensure the highest level of resilience across three availability zones. When Event Streams is provisioned for Satellite, 2 TB of storage is allocated from your configured block storage infrastructure for each of the three replicas (availability zones). This is equivalent to deploying 6 TB of storage if you run your own Apache Kafka cluster with the same replication policy enabled.

In addition to the message data retention block storage, storage is allocated by Event Streams for managing your message data and for monitoring the operation of the Event Streams service instance.

Specific block storage capacity amounts and supported storage classes are detailed in the following description.
6. Provisioning of Event Streams service instance completes and is ready to use.







 Before you begin 



1. Refer to the [Satellite usage requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-requirements).
2. Set up the [IBM Cloud command line interface (CLI)](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-cli), the plug-in for Satellite commands, and other related CLIs.
3. Event Streams uses block storage for retention of message data, management of message data, and for monitoring the operation of the Event Streams service instance. During the provision of the Event Streams service instance, the block storage configuration completes. To prepare for that configuration, review the following information.



1. The performance of the hosts, network latency, and block storage performance can all impact maximum throughput. As you review the following block storage information and select a storage class to achieve a maximum throughput, select block storage that provides a minimum of 4 IOPS per GB of storage and that can support 75 MB/s disk writes and 25 MB/s disk reads concurrently.
2.
For more information, see [Overview: Publishing and deploying your assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish-overview).

Add variables to links
: When including a link in an assistant response, you can now access and use variables. In the URL field for a link, type a dollar sign ($) character to see a list of variables to choose from.





 25 October 2021 

Facebook and Slack integrations now available
: The new Watson Assistant now includes integrations for [Facebook Messenger](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-facebook) and [Slack](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-slack).

Analytics for draft and live environments
: The Analyze page now lets you see analytics data for either the draft or live environments. For more information, see [Use analytics to review your entire assistant at a glance](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-analytics-overview).





 7 October 2021 

The new Watson Assistant
: The new Watson Assistant is now available! This new experience, focused on using actions to build customer conversations, is designed to make it simple enough for anyone to build a virtual assistant. Building, testing, publishing, and analyzing your assistant can all now be done in one simple and intuitive interface.



* New navigation provides a workflow for building, previewing, publishing, and analyzing your assistant.
* Each assistant has a home page with a task list to help you get started.
* Build conversations with actions, which represent the tasks you want your assistant to help your customers with. Each action contains a series of steps that represent individual exchanges with a customer.
* A new way to publish lets you review and debug your work in a draft environment before going live to your customers.
* Use a new suite of analytics to improve your assistant. Review which actions are being completed to see what your customers want help with, determine if your assistant understands and addresses customer needs, and decide how can you make your assistant better.
Note that $REGION would also include any network type specifications, so sending a request to a bucket in us-south using the private network would require setting the variable to private.us-south.



 Enable object lock on a bucket 

The Object Lock configuration is provided as XML in the body of the request. New requests will overwrite any existing replication rules that are present on the bucket.

An Object Lock configuration must include one rule.



 Header Type Description 

 Content-MD5 String Required: The base64 encoded 128-bit MD5 hash of the payload, which is used as an integrity check to ensure that the payload wasn't altered in transit. 



The body of the request must contain an XML block with the following schema:



 Element Type Children Ancestor Constraint 

 ObjectLockConfiguration Container ObjectLockEnabled, Rule None Required Limit 1. 
 ObjectLockEnabled String None ObjectLockConfiguration Required The only valid value is Enabled (case-sensitive). 
 Rule Container DefaultRetention ObjectLockConfiguration Limit 1 
 DefaultRetention Container Days, Mode, Years Rule Limit 1. 
 Days Integer None DefaultRetention The number of days that you want to specify for the default retention period. Cannot be combined with Years. 
 Mode String None DefaultRetention Only COMPLIANCE is supported at this time (case-sensitive). 
 Years Integer None DefaultRetention The number of years that you want to specify for the default retention period. Cannot be combined with Days. 



This example will retain any new objects for at least 30 days.

curl -X "PUT" "https://$BUCKET.s3.$REGION.cloud-object-storage.appdomain.cloud/?object-lock" 
-H 'Authorization: bearer $TOKEN' 
-H 'Content-MD5: exuBoz2kFBykNwqu64JZuA==' 
-H 'Content-Type: text/plain; charset=utf-8' 
-d $'<ObjectLockConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<ObjectLockEnabled>Enabled</ObjectLockEnabled>
<Rule>
Provisioning an instance 

Before you can monitor and manage event data with IBM Cloud Activity Tracker, you must provision an instance of the service in IBM Cloud.

To provision an IBM Cloud Activity Tracker instance in a Public Cloud region, consider the following information:



* You must select the service plan that is associated with the instance, the region where your events are collected, and the plan that determines the retention period for your events. You can choose from 7, 14, or 30-day retention periods. Alternatively, IBM Cloud Activity Tracker offers a Lite plan that you can use to view your events as they pass through the system. You can view events by using event tailing. You can also design filters to prepare for upgrading to a longer retention period plan. This plan has a 0-day retention period.
* Your user ID must have permissisons to provision a service in a resource group. [Learn more](https://cloud.ibm.com/docs/services/activity-tracker?topic=activity-tracker-iamgroups).
* You must decide if you want your instance to be accessible through both public and private endpoints, or only private endpoints.



You can only provision 1 instance of the service per IBM Cloud region.



 Provisioning an instance through the Observability dashboard 

To provision an instance from the Observability dashboard in the IBM Cloud, complete the following steps:



1. [Log in to your IBM Cloud account](https://cloud.ibm.com/login).

After you log in with your user ID and password, the IBM Cloud UI opens.
2. Go to the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/icons/icon_hamburger.svg). Then, select Observability to access the Observability dashboard.
3. Select Activity Tracker, then click Create instance.
4. Enter a name for the service instance.
5.