vania-janet/multiturn-rag-retrieval-data huggingface dataset:
They can be configured to a notification such as an email. As you check the health of the hosts and VM objects, review the alarms, decide whether a notification is needed, and configure as required. You need to be notified for only the most important or critical issues. Consider the following case: do I want to be notified of this issue at 2 AM or can it wait until normal working hours? Too many notifications are considered as "noise" and human nature is to ignore all alarms. 
 Cluster CPU and memory capacity and utilization check Review the capacity and utilization metrics for the cluster's CPU and memory. Use vCenter to navigate to each cluster in turn and selecting Monitor, then Performance. Review the graphs and statistics to ensure that your cluster has enough resources to satisfy demand. You must base demand on maintaining enough capacity for VMs to burst when needed, a vSphere ESXi host to fail, and for VMs to be added according to your known service requests. 
 Datastore capacity and utilization check Review the capacity and utilization metrics for the datastores. Use vCenter to navigate to each datastore in turn and selecting Monitor, Performance, Space. Review the graphs and statistics to ensure that your datastore has enough space to satisfy demand. Demand should be based on maintaining enough capacity a vSphere ESXi host to fail (for a vSAN™ cluster) and for VMs to be added according to your known service requests. 
 Datastore performance check Review the performance metrics for the datastores. Use vCenter to navigate to each datastore in turn and selecting: Monitor, Performance, Performance, Real-time. Review the graphs and statistics to ensure that your datastore performance baseline is expected and that any changes can be accounted for. Investigate any abnormalities. 
 Bare metal server firmware Best practices recommend installing the latest firmware updates for your bare metal server hosts. Check for firmware updates on the bare metal server hosts by using the Update Firmware option in the IBM Cloud portal. On the page that is displayed, review the current and update version for system board and hard disk drives and see whether updates are available. If they are, plan to update the firmware in your next maintenance window.
SOC 2 reports provide details about the nature of internal controls that are implemented to protect customer-owned data. For more information, see [IBM Cloud compliance programs](https://www.ibm.com/cloud/compliance/global).





 25 February 2021 

Search skill can emphasize the answer
: You can configure the search skill to highlight text in the search result passage that Discovery determines to be the exact answer to the customer's question. For more information, see [Creating a search skill](https://cloud.ibm.com/docs/assistant?topic=assistant-skill-search-add).

Integration changes
: The following changes were made to the integrations:



* The name of Preview link integration changed to Preview.
* The Web chat and Preview integrations are no longer added automatically to every new assistant.

The integrations continue to be added to the My first assistant that is generated for you automatically when you first create a new service instance.



Message and log webhooks are generally available
: The premessage, postmessage, and log webhooks are now generally available. For more information about them, see [Webhook overview](https://cloud.ibm.com/docs/assistant?topic=assistant-webhook-overview).





 11 February 2021 

The user_id value is easier to access
: The user_id property is used for billing purposes. Previously, it was available from the context object as follows:



* v2: context.global.system.user_id
* v1: context.metadata.user_id



The property is now specified at the root of the /message request in addition to the context object. The built-in integrations typically set this property for you. If you're using a custom application and don't specify a user_id, the user_id is set to the session_id (v2) or conversation_id(v1) value.

Digression bug fix
: Fixed a bug where digression setting changes that were made to a node with slots were not being saved.





 5 February 2021 

Documentation update
Tags are uniquely identified by a CRN identifier. Tags have a name, which must be unique within a billing account. You can create tags in key:value pairs or label format.





 Monitoring your resources 

Observability offers a single location where you can monitor and observe your applications and services in IBM Cloud.

With the IBM® Log Analysis service, you can add log management capabilities to your IBM Cloud architecture and you can manage system and application logs. It offers advanced features to monitor and troubleshoot, define alerts, and design custom dashboards. For more information, see [Getting started with IBM Log Analysis](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-getting-started).

You can gain operational visibility into the performance and health of your applications, services, and platforms with the IBM Cloud Monitoring service. It offers a full stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards. For more information, see [Getting started with IBM Cloud Monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-startedgetting-started).





 Monitoring your account 

Use the IBM Cloud® Activity Tracker service to monitor the activity of your IBM Cloud account, investigate abnormal activity and critical actions, and comply with regulatory audit requirements. In addition, you can be alerted on actions as they happen. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see [Getting started with IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started).





 Viewing status 

The IBM Cloud Status page is the central place to find all unplanned incidents, planned maintenance, announcements, and security bulletin notifications about key events that affect the IBM Cloud platform. You can filter these categories by selecting specific locations, components, types of ongoing events, or by using keyword searches. For more information, see [Viewing cloud status](https://cloud.ibm.com/docs/get-support?topic=get-support-viewing-cloud-status).





 Notification preferences
Logging and monitoring <br><br> * [Activity Tracker Event Routing](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-iam)<br> * [Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-access-management)<br> * [Flow Logs for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls)<br><br><br> <br><br> * [Activity Tracker Event Routing](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-iam) <br> [Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-access-management)<br><br><br> 
 Integration <br><br> * [Event Streams](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-security)<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-iam)<br> * [Hyper Protect DBaaS for PostgreSQL](https://cloud.ibm.com/docs/hyper-protect-dbaas-for-postgresql?topic=hyper-protect-dbaas-for-postgresql-iam)<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/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.
For more information on how to interpret this view, see [About Nodes Overview](https://docs.sysdig.com/en/docs/sysdig-monitor/advisor/overview/nodes-data/).





 Monitoring clusters by namespace 

When you choose to monitor your clusters by namespace, you can select more filters to display data by workload, or you can choose any of the following dashboards:



* Workload Status & Performance
* Pod Status & Performance
* Pod Rightsizing & Workload Capacity Optimization
* Namespace Overview
* Workloads CPU Usage and Allocation
* Workloads Memory Usage and Allocation



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 clusters by workloads 

When you choose to monitor your 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.
Monitor archiving with Activity Tracker 

You can monitor archiving of an Log Analysis instance by monitoring the service ID that is used to write data into IBM Cloud Object Storage (COS) by using the Activity Tracker service.



 Prereqs 



 Activity Tracker service 



* You must have an Activity Tracker instance provisioned that receives events from the COS bucket that you use for archiving. Normally this instance is in the same region as the COS bucket.
* You must have a paid service plan for the IBM Cloud Activity Tracker service. [Learn more](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_plans).
* Check that your user ID has permissions to launch the web UI and create views and alerts in the Activity Tracker instance. The following table lists the minimum roles that a user must have to be able to launch the IBM Cloud Activity Tracker web UI, and manage resources:





Table 1. IAM roles

 Role Permission granted 

 Platform role: Viewer Allows the user to view the list of service instances in the Observability dashboard. 
 Service role: standard-user <br>or <br>Service role: manager Allows the user to launch the web UI and configure resources. 



For more information on how to configure policies for a user, see [Granting user permissions to a user or service ID](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-iam_view_events).





 IBM Cloud Object Storage service 



* You must have enabled collection of data events for the bucket where you are archiving data for the Log Analysis instance. Make sure the events are saved to your IBM Cloud Activity Tracker instance.

You must enable write data events to monitor upload of objects to the bucket.

You must enable read data events to monitor download of objects from the bucket.
* You must have access to view the bucket CRN.
* You must have access to view the service ID CRN value that is associated with the service credential that is used to configure archiving in Log Analysis.









 Configure an alert to monitor archiving 



 Step 1. Get the service ID
Activity Tracker events for Natural Language Understanding 

You can use the IBM Cloud® Activity Tracker service to track how users and applications interact with Natural Language Understanding in IBM Cloud®.

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. The events that are collected comply with the Cloud Auditing Data Federation (CADF) standard. For more information, see the [getting started tutorial for IBM Cloud Activity Tracker](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-getting-startedgetting-started).



  List of events 



Table 1. Actions that generate events

 Action                                         Description    

 natural-language-understanding.model.create    Create a model 
 natural-language-understanding.model.delete    Delete a model 







  Viewing events 

Events that are generated by an instance of the Natural Language Understanding service are automatically forwarded to the IBM Cloud Activity Tracker service instance that is available in the same location.

IBM Cloud Activity Tracker can have only one instance per location. To view events, you must access the web UI of the IBM Cloud Activity Tracker service in the same location where your service instance is available. For more information, see [Launching the web UI through the IBM Cloud UI](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-launchlaunch_step2).
Instead of guessing which node to process, your assistant shares a list of the best node options with the user, and asks the user to pick the correct one.

![Shows a sample conversation between a user and the assistant, where the assistant asks for clarification from the user.](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/disambig-demo.png)

If enabled, disambiguation is not triggered unless the following conditions are met:



* The confidence scores of the runner-up intents detected in the user input are close in value to the confidence score of the top intent.
* The confidence score of the top intent is above 0.2.



Even when these conditions are met, disambiguation does not occur unless two or more independent nodes in your dialog meet the following criteria:



* The node condition includes one of the intents that triggered disambiguation. Or the node condition otherwise evaluates to true. For example, if the node checks for an entity type and the entity is mentioned in the user input, it is eligible.
* There is text in the node's external node name field.



Learn more



* [Disambiguation example](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-runtimedialog-runtime-disambig-example)
* [Enabling disambiguation](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-runtimedialog-runtime-disambig-enable)
* [Choosing nodes](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-runtimedialog-runtime-choose-nodes)
* [Handling none of the above](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-dialog-runtimedialog-runtime-handle-none)
Monitoring streaming to Event Streams 

You can use IBM Cloud Monitoring and IBM Cloud Activity Tracker to monitor streaming of data from your Log Analysis instance.



 Monitoring streaming by using IBM Cloud Monitoring 

Event Streams is integrated with the Monitoring service. Monitoring provides a default template that you can customize to monitor the Event Streams instance, how data is streamed out of Log Analysis and consumed by any application or service that is subscribed to Event Streams.

Complete the following steps to monitor the Event Streams instance:



1. Check that you have an instance of the Monitoring in the same region as your Event Streams instance. This instance must be configured to collect platform metrics. For more information, see [Enabling platform metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling).
2. [Launch the Monitoring UI](https://cloud.ibm.com/docs/monitoring?topic=monitoring-launch).
3. In the Dashboards section, go to Dashboard templates and select the template IBM Event Streams (Enterprise).
4. Create a copy of the temnplate by clicking Create custom dashboard.

You can use the metric Topic bytes in per second to see how data is sent by Log Analysis to Event Streams.

You can use the metric Topic bytes out per second to see how data is consumed by any application or service that is subscribed to Event Streams.
5. (Optional) Edit the panel Topic bytes in per second.

![Edit panel.](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/streaming-topic-metric.png)

Then, customize the metric to see data per topic.

![Customize metric.]
[Shows the Analytics>User conversations page with a logged conversation with Buenos días (in es) input](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/webhook-check-language.png)





 Example 2 

This example shows you how to check the language of the incoming message, and if it's not English, translate it into English before submitting it to the assistant. Doing so can be useful if the assistant's conversational skill is in English.

Define a sequence of web actions in IBM Cloud Functions. The first action in the sequence checks the language of the incoming text. The second action in the sequence translates the text from its original language into English.

In the premessage webhook configuration page, the following values are specified:



* URL: https://us-south.functions.appdomain.cloud/api/v1/web/e97d2516-5ce4-4fd9-9d05-acc3dd8ennn/default/translation_sequence
* Secret: none
* Header name: Content-Type
* Header value: application/json



The node.js code for the first web action in your sequence looks as follows:

let rp = require("request-promise");

function main(params) {
console.log(JSON.stringify(params))
if (params.payload.input.text !== '') {
const options = { method: 'POST',
url: 'https://api.us-south.language-translator.watson.cloud.ibm.com/instances/572b37be-09f4-4704-b693-3bc63869nnnn/v3/identify?version=2018-05-01',
auth: {
'username': 'apikey',
'password': 'nnn'
},
headers: {
To monitor how the IBM Cloud Monitoring service is used and the costs associated to its usage, see [Viewing your usage](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-viewingusageviewingusage).

All metrics that start with sysdig_* and kube_ are collected automatically by an agent and are included in the agent price.





 Service plans 

The following service plans are available when you provision an instance of the IBM Cloud Monitoring service:



 Lite plan 

You can provision a Monitoring instance with the Lite service plan to try out the Monitoring service for free for 30 days.

After 30 days you must upgrade the instance to a graduated tier plan to continue working with the Monitoring service or delete it.





 Graduated tier plan 

The graduated tier service plan is billed based on the number of hosts that you monitor, the agent mode that is configured per host, the number of containers, the number of API calls, and the number of time series collected.

The following table outlines the cost per host by agent mode and what is included in the price:



Table 4. Cost per host and agent mode

 Agent mode Cost per host Default infrastructure metrics (CPU, memory, disk, and network) Includes up to 1K time-series (Prometheus, JMX, appchecks, StatsD) Monitoring of 50 containers 1M API calls 

 Agent for non-orchestrated environments $9.36 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) 
 Agent for orchestrated environments $36 ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/220cdcbf6f4421bd7fee83fd1028048dba3f16c8/monitoring//images/checkmark-icon.svg) !
[Shows the Analytics>User conversations page with a logged conversation with Buenos días (in es) input](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/webhook-check-language.png)





 Example 2 

This example shows you how to check the language of the incoming message, and if it's not English, translate it into English before submitting it to the assistant. Doing so can be useful if the assistant's conversational skill is in English.

Define a sequence of web actions in IBM Cloud Functions. The first action in the sequence checks the language of the incoming text. The second action in the sequence translates the text from its original language into English.

In the premessage webhook configuration page, the following values are specified:



* URL: https://us-south.functions.appdomain.cloud/api/v1/web/e97d2516-5ce4-4fd9-9d05-acc3dd8ennn/default/translation_sequence
* Secret: none
* Header name: Content-Type
* Header value: application/json



The node.js code for the first web action in your sequence looks as follows:

let rp = require("request-promise");

function main(params) {
console.log(JSON.stringify(params))
if (params.payload.input.text !== '') {
const options = { method: 'POST',
url: 'https://api.us-south.language-translator.watson.cloud.ibm.com/instances/572b37be-09f4-4704-b693-3bc63869nnnn/v3/identify?version=2018-05-01',
auth: {
'username': 'apikey',
'password': 'nnn'
},
headers: {