vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* The speech_detector_sensitivity parameter adjusts the sensitivity of speech activity detection. You can use the parameter to suppress word insertions from music, coughing, and other non-speech events.
* The background_audio_suppression parameter suppresses background audio based on its volume to prevent it from being transcribed or otherwise interfering with speech recognition. You can use the parameter to suppress side conversations or background noise.



You can use the parameters individually or together. They are available for all interfaces and for most language models. For more information about the parameters, their allowable values, and their effect on the quality and latency of speech recognition, see [Speech activity detection](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-detection).

New broadband and narrowband models for Dutch and Italian
: The service now supports broadband and narrowband models for the Dutch and Italian languages:



* Dutch broadband model (nl-NL_BroadbandModel)
* Dutch narrowband model (nl-NL_NarrowbandModel)
* Italian broadband model (it-IT_BroadbandModel)
* Italian narrowband model (it-IT_NarrowbandModel)



Dutch and Italian language models are generally available (GA) for speech recognition and for language model and acoustic model customization. For more information about all available language models, see



* [Supported previous-generation language models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-modelsmodels-supported)
* [Language support for customization](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-support)



Support for speaker_labels parameter for German and Korean
: The service now supports speaker labels (the speaker_labels parameter) for German and Korean language models. Speaker labels identify which individuals spoke which words in a multi-participant exchange. For more information, see [Speaker labels](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-speaker-labels).

Improved speech recognition for Japanese narrowband model
* Consider setting up a [monitoring tool](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorview_metrics) such as IBM Cloud Monitoring and creating alerts for your workloads when they need more resources.



6. [View your usage](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-viewingusageviewingusage) to continuously refine how you consume IBM Cloud services.
7. [Set spending notifications](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-spending).
If none of the conditions evaluates to true, then the response from the last node in the tree, which typically has a special anything_else condition that always evaluates to true, is returned.

You can disrupt the standard first-to-last flow in the following ways:



* By customizing what happens after a node is processed. For example, you can configure a node to jump directly to another node after it is processed, even if the other node is positioned earlier in the tree. See [Defining what to do next](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-overviewdialog-overview-jump-to) for more information.
* By configuring conditional responses to jump to other nodes. See [Conditional responses](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-overviewdialog-overview-multiple) for more information.
* By configuring digression settings for dialog nodes. Digressions can also impact how users move through the nodes at run time. If you enable digressions away from most nodes and configure returns, users can jump from one node to another and back again more easily. See [Digressions](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-runtimedialog-runtime-digressions) for more information.







 Sample dialog 

This diagram shows a mockup of a dialog tree that is built with the graphical user interface dialog editor.

![A sample dialog tree with example content](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/dialog-depiction-full.png)

The dialog tree in this diagram contains two root dialog nodes. A typical dialog tree would likely have many more nodes, but this depiction provides a glimpse of what a subset of nodes might look like.



* The first root node conditions on an intent value.
* [Forwarding logs to your own server over the tls protocol](https://cloud.ibm.com/docs/containers?topic=containers-healthenable-forwarding-tls)
* [Filtering logs that are forwarded](https://cloud.ibm.com/docs/containers?topic=containers-healthfilter-logs)
* [Verifying, updating, and deleting log forwarding](https://cloud.ibm.com/docs/containers?topic=containers-healthverifying-log-forwarding)





[Monitoring cluster health](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorhealth-monitor)



* [Choosing a monitoring solution](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorview_metrics)
* [Forwarding cluster and app metrics to IBM Cloud Monitoring](https://cloud.ibm.com/docs/containers?topic=containers-health-monitormonitoring)
* [Viewing cluster states](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorstates)



* [Master states](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorstates_master)



* [Setting up IBM Cloud® Monitoring alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitormonitoring-alerts)



* [App alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorapp-level-alerts)
* [Worker node alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorworker-node-level-alerts)
* [Zone alerts](https://cloud.ibm.com/docs/containers?topic=containers-health-monitorzone-level-alerts)
Logging and monitoring <br><br> * [Activity Tracker Event Routing](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-mng-data)<br> * [Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-mng-data)<br> * [Flow Logs for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-about)<br><br><br> <br><br> * [Activity Tracker Event Routing](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-mng-data)<br> * [Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-mng-data)<br><br><br> 
 Integration <br><br> * [Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-managing_encryption)<br><br><br> 
 Databases <br><br> * [Hyper Protect DBaaS for MongoDB](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-mongodb?topic=hyper-protect-dbaas-for-mongodb-hpcs-byok)<br> * [Hyper Protect DBaaS for PostgreSQL](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-postgresql?topic=hyper-protect-dbaas-for-postgresql-hpcs-byok)<br><br><br> 







 Related controls in IBM Cloud Framework for Financial Services 

The following [IBM Cloud Framework for Financial Services controls](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-aboutframework-control-requirements) are most related to this guidance.
(https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/monitoring-current_operations.png)

Figure 4. Monitoring - Current Operations

Denied Requests tab



* Shows the number of requests that were denied in a given second.
* Shows the response, 429: too many requests.
* Requests are denied because they exceed the provisioned throughput capacity that is allocated to the instance. The graphs are broken down by reads, writes, and global queries.



Zoom

![Monitoring - Denied Requests shows the number of requests that were denied in a given second. Shows 429: too many requests. Requests are denied because they exceed the provisioned throughput capacity that is allocated to the instance.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/monitoring-denied_requests.png)

Figure 5. Monitoring - Denied Requests

Monitoring helps you recognize that a change to the provisioning in your plan might be advisable. For example, if you frequently approach the maximum number of database reads, then you can modify the capacity for the instance through the [Capacity](https://cloud.ibm.com/docs/services/Cloudant?topic=Cloudant-ibm-cloud-publicviewing-and-changing-capacity) UI.







 Data usage 

The data storage that is measured for billable purposes for an IBM Cloudant instance is inclusive of both JSON data, indexes, and attachments.



 Data storage included 

This value is the storage capacity that is included in the plan. The Lite plan has a hard limit of 1 GB allowed. The paid Standard plan includes 20 GB for free and any additional data that is stored is metered for billing.





 Data overage 

All Lite and Standard plans are monitored for disk space used.
You can see the dispatch status as well as delivered and opened information for individual devices. For more information, see [Logging for Event Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-logs).





 Push charges 

The IBM Cloud push service has two components to pricing: a destination instance fee and a consumption price.

The destination instance fee is a fixed amount charged monthly. Every push destination added to your Event Notifications instance incurs the fee.

The consumption price is based on outbound digital messages. Every push notification that is sent by the IBM Cloud push service counts as one outbound digital message and is charged. For example, you send messages to two platforms (iOS and Android) and you create a subscription that has 100 phone numbers. The subscription topic received 1000 events during the month:

Destination instances: 2

Consumption:

Total Outbound Digital messages = (number of phone numbers) x (topic events)

In the example, the total outbound digital messages are:

100 x 1000 = 100000 outbound digital messages

You are charged for messages that are successfully sent by the IBM Cloud push service to the push provider regardless of whether the message was successfully delivered to the local device. So vet your device list carefully to prevent unnecessary charges.

You can monitor your push usage by setting up a monitoring dashboard through the Actions menu in the Event Notifications dashboard. For more information, see [Monitor Event Notifications service metrics with IBM Cloud Monitoring](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-monitoring).



 Push charges for pre-production destination 

The IBM Cloud push service has two components to pricing: a destination instance fee and a consumption price.

A pre-production destination instance fee is charged monthly. Every pre-production destination added to your Event Notifications instance incurs the fee.

Consumption: Only 500 devices or 5000 outbound digital messages is permitted per pre-production destination. If either the number of devices or the number of outbound digital messages exceeds the permitted limit, the permitted number of devices is moved by additional 500 devices or by additional 5000 messages and charged.
barge_in_occurred Boolean Whether barge-in occurred during the turn. 
 streaming_statistics Object Information and statistics related to Text to Speech synthesis and playback. See [assistant_interaction_summaries.turns].response.streaming_statistics](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-cdr-log-referencecdr-log-reference-response-streaming_statistics). 





 Mapping between CDR and Watson Assistant response types 

The values of the type property map to Watson Assistant response types as follows:



 CDR response type Watson Assistant response type 

 text_to_speech text 
 url audio 
 dtmf dtmf, command_info.type : send 
 sms user_defined, vgwAction.command : vgwActSendSMS 
 transfer connect_to_agent 
 text_to_speech_config text_to_speech, command_info.type : configure 
 speech_to_text_config speech_to_text, command_info.type : configure 
 unpause_speech_to_text start_activities, type:speech_to_text_recognition 
 pause_speech_to_text stop_activities, type:speech_to_text_recognition 
 unpause_dtmf start_activities, type:dtmf_collection 
 pause_dtmf stop_activities, type:dtmf_collection 
 enable_speech_barge_in text_to_speech, command_info.type : enable_barge_in 
 disable_speech_barge_in text_to_speech, command_info.type : disable_barge_in 
 enable_dtmf_barge_in dtmf, command_info.type : enable_barge_in 
 disable_dtmf_barge_in dtmf, command_info.type : disable_barge_in 
 hangup end_session 







 assistant_interaction_summaries.turns[].response.streaming_statistics 

The assistant_interaction_summaries.turns[].response.streaming_statistics object contains the following properties:
For example, if an incoming notification is split into three SMS segments, and the message is sent to five subscribed phone numbers, then the total consumed SMS units for the incoming message is as follows:

Total SMS units = (Number of Segments) x (Number of phone numbers) x (SMS Unit for the country)

In the example, the total SMS units for messages that are sent to destination numbers in the United States is:

3 x 5 x 1 = 15 SMS units

You are charged for messages that are successfully sent by the IBM Cloud SMS service to the local SMS provider regardless of whether the message was successfully delivered to the local device. So verify your phone number list carefully to prevent unnecessary charges.

You can monitor your SMS usage by setting up a monitoring dashboard through the Actions menu in the Event Notifications dashboard. See [Monitor Event Notifications service metrics with IBM Cloud Monitoring](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-monitoring) for details.
[Learn more about metric streaming](https://cloud.ibm.com/docs/monitoring?topic=monitoring-data_streaming)





 8 September 2021 

Secure support for new and updated compliance standards
: New and updates compliance standards are supported.



* Updates to PCI DSS V3.2.1.
* New NIST 800-171 rev2 compliance.







 31 August 2021 

Agent update
: Added support for agent version 11.4.1. To see the the agent versions that are available, see the [monitoring agent Release Notes](https://docs.sysdig.com/en/sysdig-agent-release-notes.html).





 12 August 2021 

Secure support for Inline Scanner
: V2.4.6 is supported which adds support for images with manifest schema V1.





 10 August 2021 

Monitoring integrations
: You can monitor integrations using PromCat.

Alert enhancements
: The following alert enhancements are available:



* The alert library provides a recommended list of alerts you can configure based on the services running in your infrastructure.
* The alerts page has been enhanced. Visual cues have been added to identify alerts that have not been resolved. Alerts can also be grouped based on the service they represent.



Dashboard enhancements
: The following Kubernetes dashboard enhancements have been made:



* Workload dashboards are refreshed.
* Changes to the panel location and color coding.
* Workflow simplification.
* Improved capacity planning.
* Easier to read text boxes.







 30 July 2021 

Secure support for Inline Scanner
: V2.4.5 is supported which fixes an issue when using --verbose with --format json resulting in corrupted JSON output.





 28 July 2021 

Secure support for Inline Scanner
: V2.4.4 is supported including the following updates:



* Security fixes.
* Adding a retry mechanism when pulling images from registries.
* Adding the ability to write a JSON log to a file.
* Fixed a malware scan issue.
* Check whether account has at least one VPN or Direct Link configured
* Check whether App ID redirect URIs are using HTTPS only
* Check whether Cloud Internet Services (CIS) has TLS mode set to End-to-End CA signed
* Check whether Application Load Balancer for VPC pool uses the HTTPS protocol for HTTPS listeners
* Check whether Application Load Balancer for VPC uses HTTPS (SSL & TLS) instead of HTTP







 NIST supplemental guidance 

Trusted paths are mechanisms by which users (through input devices) can communicate directly with security functions of information systems with the requisite assurance to support information security policies. The mechanisms can be activated only by users or the security functions of organizational information systems. User responses via trusted paths are protected from modifications by or disclosure to untrusted applications. Organizations employ trusted paths for high-assurance connections between security functions of information systems and users (e.g., during system logons). Enforcement of trusted communications paths is typically provided via an implementation that meets the reference monitor concept.
For more information about these and all available voices, see [Languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices).

New support for Activity Tracker
: The service now supports the use of Activity Tracker events for all customization operations. IBM Cloud Activity Tracker records user-initiated activities that change the state of a service in IBM Cloud. You can use this service to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. In addition, you can be alerted about actions as they happen. For more information, see [Activity Tracker events](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-at-events).





 18 December 2019 

New standard Arabic, Chinese, and Netherlands Dutch voices
: The service now supports six new standard voices in three new languages:



* Arabic:ar-AR_OmarVoice
* Chinese (Mandarin):zh-CN_LiNaVoice, zh-CN_WangWeiVoice, and zh-CN_ZhangJingVoice
* Netherlands Dutch:nl-NL_EmmaVoice and nl-NL_LiamVoice



The following information applies to these new standard voices:



* The new voices are beta functionality. The voices might not be ready for production use and are subject to change. They are initial offerings that are expected to improve in quality with time and usage.
* The voices do not support the <mark> element and timings parameter that are available with the WebSocket interface.
* The voices do not support customization or the /v1/pronunciation method.
* The voices do not support expressive SSML or voice transformation SSML.
* The voices do support all other SSML elements. However, they support only the International Phonetic Alphabet (IPA), not IBM Symbolic Phonetic Representation (SPR), with the <phoneme> element.



For more information about these and all available voices, see [Languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voices).





 12 December 2019 

Full support for IBM Cloud IAM
For more information on how to interpret this view, see [About Namespaces Overview](https://docs.sysdig.com/en/docs/sysdig-monitor/advisor/overview/namespaces-data/).





 Monitoring Kubernetes clusters by workloads 

When you choose to monitor your Kubernetes clusters by workloads, you can choose any of the following dashboards:



* Container Resource Usage & Troubleshooting
* Pod Status & Performance
* Pod Rightsizing & Workload Capacity Optimization
* Workload Status & Performance
* Deployment Overview
* Pod Overview
* Workloads CPU Usage and Allocation
* Workloads Memory Usage and Allocation



For more information on how to interpret this view, see [About Workloads Overview](https://docs.sysdig.com/en/docs/sysdig-monitor/advisor/overview/workloads-data/).







 Step 5: Next steps 



* Create a custom dashboard. For more information, see [Working with dashboards](https://cloud.ibm.com/docs/monitoring?topic=monitoring-dashboardsdashboards).
* Learn about alerts. For more information, see [Working with alerts](https://cloud.ibm.com/docs/monitoring?topic=monitoring-monitoringmonitoring_alerts).
* Learn how to manage logs from your cluster. See [Logging with Kubernetes clusters](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-kube).
* Learn about the IBM Cloud Monitoring Workload Protection functionality to find and prioritize software vulnerabilities, detect and respond to threats, and manage configurations, permissions and compliance from source to run. See [Getting started with IBM Cloud® Security and Compliance Center Workload Protection](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-getting-started).
At that point, the system can respond by updating the relevant failover metadata to route traffic to the service instance in the other region. Once a failover happens, you can decide to continue using the new region as the active instance, or if you want to resume using the initial region once it has stabilized.

For an active/active topology, some form of a load balancing can be used, where two or more service instances in unique regions always receive a percentage of traffic. Additional logic would need to be established to determine when to pull a region out of rotation. This monitoring logic could use a [circuit break pattern](https://martinfowler.com/bliki/CircuitBreaker.html) similar to the active/passive configuration or rely on a separate dedicated monitoring framework that determines region health. Also similar to active/passive, determining when to insert a region back in rotation would need to be considered as well.





 Failover for v2 stateful API 

Failover for the v2 stateful API is similar to stateless, with these details to consider:



* The state of a given conversation is persisted by Watson Assistant in a database that is tied to a particular region. As such, a failover for the stateful v2 /message may more disruptive.
* For an active/passive topology, you should assume that all in-progress conversations are ended.
* For an active/active topology, given the region-locked persistence constraints of the v2 stateful /message architecture, all turns (/message API calls) of a given conversation (session) should occur within the same region.