vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Best practices for monitoring status 

To create a plan and stay informed, use the following best practices for monitoring the status of IBM Cloud®. Ongoing incidents or planned maintenance windows that impact a finite set of accounts do not display on the Status page. The notifications for those events are published only to the customer [Notifications page](https://cloud.ibm.com/notifications).



 Check for upcoming maintenance windows 

Check for upcoming maintenance windows posted on the IBM Cloud console Dashboard page, at least one time every 24 hours, by using one of the following options:



* Check out the Planned maintenance widget on the [Dashboard](https://cloud.ibm.com), and click View events to view all planned maintenance.
* Go directly to the [Status - Planned maintenance page](https://cloud.ibm.com/status?selected=maintenance).







 Check for current maintenance windows or an incident in progress 

If you suspect that IBM Cloud isn't functioning as expected, check the Status page for current maintenance windows or an incident in progress. To report an incident that isn't already listed on the Status page, open a support case. For more information about opening a support case, see [Creating support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case).

In most cases, IBM Cloud can be used normally during a maintenance window. However, minor interruptions of a service can't always be avoided. Running applications typically remain available even if the application management functions, such as starting and stopping apps, are temporarily interrupted. To maximize the availability of your running applications, run at least three instances of each application.





 Take advantage of multiple IBM Cloud locations 

All users of IBM Cloud automatically have access to the Dallas, London, Frankfurt, Sydney, Washington DC, and Tokyo locations. The IBM Cloud Global Operations team manages all locations to avoid maintenance impacts and minimize the risk of incidents that affect all locations at the same time.

You can check the status of your locations from the dashboard on the IBM Cloud status widget. To view specific events, click View all.





 Subscribing to email notifications
Auditing events 

As a security officer, auditor, or manager, you can use the IBM Cloud Activity Tracker service to track how users and applications interact with the Event Notifications service in IBM Cloud.

IBM Cloud Activity Tracker records user-initiated activities that change the state of a service in IBM Cloud. Use this service to investigate abnormal activity and critical actions and to comply with regulatory audit requirements. You are also 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?topic=activity-tracker-getting-started).



 List of events 

The following list of Event Notifications data events is sent to IBM Cloud Activity Tracker.



Table 1. Overview of Event Notifications actions that generate IBM Cloud Activity Tracker events

 Action Description 

 event-notifications.topics.read An event is generated when a topic is retrieved. 
 event-notifications.topics.create An event is generated when a topic is created. 
 event-notifications.topics.list An event is generated when you retrieve a list of topics. 
 event-notifications.topics.update An event is generated when you update a topic. 
 event-notifications.topics.delete An event is generated when you delete a topic. 
 event-notifications.destinations.read An event is generated when you retrieve a destination. 
 event-notifications.destinations.create An event is generated when you create a destination. 
 event-notifications.destinations.list An event is generated when you retrieve the list of destinations. 
 event-notifications.destinations.update An event is generated when you update a destination. 
 event-notifications.destinations.delete An event is generated when you delete a destination. 
 event-notifications.sources.read An event is generated when you retrieve a source. 
 event-notifications.sources.create An event is generated when you create a source. 
 event-notifications.sources.list An event is generated when you retrieve the list of sources. 
 event-notifications.sources.update An event is generated when you update a source.
This selection gives you access to the following add-on monitoring services.



Table 2. Add-on monitoring service types

 Add-on monitoring service types Description 

 DNS Test generic nslookup on address 
 DNS CUSTOM Test nslookup for specified domain on address 
 FTP Test for FTP connection to port 21 on address 
 HTTP Test for HTTP connection to port 80 on address 
 HTTP CUSTOM Test for HTTP connection to port 80 on address, checks for given response text 
 HTTPS Test for HTTP connection to port 443 on address 
 IMAP Test for IMAP connection on address 
 LDAP Test for LDAP connection on address 
 NNTP Test for NNTP connection on address 
 POP Test for POP connection on address 
 SMTP Test for SMTP connection on address 
 SSH Test for SSH connection to port 22 on address 
 TCP CUSTOM Test for TCP connection to specified port on address 
 TELNET Test for telnet connection to port 23 on address 
 UDP SIP Test for UDP connection to specified port on address 









 Viewing configured monitors 

To view configured monitors, use the following steps:



1. Go to your console's device menu. For more information, see [Navigating to devices](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-navigating-devices).
2. From the Devices menu, select Device List and select the device.
3. Click the Monitoring tab. All current pings are viewable on the landing page.



The Monitoring tab is only visible if at least one monitor is configured.





 Health dashboard for Classic infrastructure 

With the health monitoring dashboard, you can see important stats about your environment that might need attention. From the health dashboard, you can quickly see the following information:



* All your devices and their associated monitoring statuses
* Quickly see any servers that might require firmware updates
* See whether any operating systems are no longer supported and if an OS reload is required





 Viewing the health dashboard for Classic infrastructure 

To view your health dashboard, use the following steps.



1. Go to your [Classic infrastructure](https://cloud.ibm.com/classic).
Plan usage is measured based on the number of monthly active users, where a user is identified by the caller's unique phone number. An MD5 hash is applied to the phone number and the 128-bit hash value is used for billing purposes.

The number of concurrent calls that your assistant can participate in at one time depends on your plan type.



Plan details

 Plan Concurrent calls 

 Enterprise 1,000 
 Plus 100 
 Trial 5 







 Troubleshooting the phone integration 

Find solutions to problems that you might encounter while using the integration.



* If you get a Forbidden message, it means the phone number that you specified when you configured the integration cannot be verified. Make sure the number fully matches the SIP trunk phone number.





 Viewing logs 

The log events that occur in the components that are used by the phone integration are written to IBM Log Analysis. To check the logs, create an instance and configure the platform logs to observe the region where your service instance is hosted.

For more information about setting up an instance, see [Provisioning an instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provision).

Currently, the Phone and SMS with Twilio integrations are the only components of your assistant that write logs to the IBM Log Analysis dashboard.

After you create the instance, get log information by completing the following steps:



1. Go to the [IBM Cloud Logging](https://cloud.ibm.com/observe/logging) page.
2. Click Options, then choose Edit platform.
3. Select the region and instance, and then click Select.
4. To open the IBM Log Analysis console, click Open Dashboard.
5. The source name of the log events is Watson.

You can apply filters or search the logs by values such as a phone number or instance ID.
Compliance monitoring 

You are required to continuously monitor for possible security flaws and changes in baseline configurations for which you should take corrective action. With [IBM Cloud® Security and Compliance Center](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-getting-started) you can embed security checks into your every day workflows to help monitor for security and compliance. By monitoring for risks, you can identify security vulnerabilities and quickly work to mitigate the impact and fix the issue. By using Security and Compliance Center along with [external integrations](https://cloud.ibm.com/security-compliance/integrations) (such as, OpenShift Compliance Operator (OSCO), Tanium, NeuVector, and so on), you can build a robust approach for monitoring for security and compliance issues.



 Using Security and Compliance Center 

Security and Compliance Center provides a number of [pre-defined profiles](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-predefined-profiles). Each profile is a collection of

controls, and each control has one or moregoals. Goals are pre-defined automated tests used to evaluate your posture against a control.

Running a scan against a specific profile does not ensure regulatory compliance. The scan is intended to provide a point in time statement of your current posture for a specific group of resources.

The IBM Cloud for Financial Services profile provides a tailored set of goals that are mapped to the [IBM Cloud Framework for Financial Services control requirements](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-aboutframework-control-requirements). This profile should always be used when leveraging the [VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-about).
Algorithm beta version (2022-06-10)
: Algorithm beta version (2022-06-10) includes a new irrelevance detection algorithm to improve off-topic detection accuracy. Utterances with similar meanings are expected to have more similar confidences in comparison to previous irrelevance detection algorithms. For example, in the Customer Care Sample Skill, the training utterance please suggest route from times square has 100% confidence at runtime. Currently in IBM Cloud, the utterance please suggest route from central park gets a low confidence and could be flagged as irrelevant. With beta version (2022-06-10), the same utterance is expected to be predicted correctly as #Customer_Care_Store_Location with a 46% confidence.





 19 May 2022 

Sign out due to inactivity setting
: Watson Assistant now uses the Sign out due to inactivity setting from Identity & Access Management (IAM). IBM Cloud account owners can select the time it takes before an inactive user is signed out and their credentials are required again. The default is 2 hours.

An inactive user will see two messages. The first message alerts them about an upcoming session expiration and provides a choice to renew. If they remain inactive, a second session expiration message appears and they will need to log in again.

For more information, see [Setting the sign out due to inactivity duration](https://cloud.ibm.com/docs/account?topic=account-iam-work-sessions&interface=uisessions-inactivity).





 18 May 2022 

Language support improvements
: Entity recognition and intent classification for Japanese and Korean languages changed to improve the reliability of Watson Assistant. You might see minor differences in how Watson Assistant handles entity recognition and intent classification. This change affects Watson Assistant workspaces that are trained after May 18, 2022. Workspaces that were trained before May 18, 2022 maintain the same behavior.

Any visible changes are most likely to be seen in dictionary-based or pattern-based entity matching. For more information about defining entities, see [Defining information to look for in customer input](https://cloud.ibm.com/docs/assistant?topic=assistant-entities).
SI-4 (4) - Inbound and Outbound Communications Traffic 



  Control requirements 

SI-4 (4) - 0
:   The information system monitors inbound and outbound communications traffic [IBM Assignment: continuously] for unusual or unauthorized activities or conditions.





  NIST supplemental guidance 

Unusual/unauthorized activities or conditions related to information system inbound and outbound communications traffic include, for example, internal traffic that indicates the presence of malicious code within organizational information systems or propagating among system components, the unauthorized exporting of information, or signaling to external information systems. Evidence of malicious code is used to identify potentially compromised information systems or information system components.
Auditing events 

As a security officer, auditor, or manager, you can use the Activity Tracker service to track how users and applications interact with the IBM Cloud Monitoring service 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-started).

IBM Cloud Monitoring automatically generates events so that you can track activity on your service instance.



 Alerts: List of management events 



Table 1. Alerts: List of activity tracker actions

 Action Description 

 sysdig-monitor.alert.create An event is created when you create an alert definition 
 sysdig-monitor.alert.read An event is created when you read an alert definition 
 sysdig-monitor.alert.update An event is created when you update an alert definition 
 sysdig-monitor.alert.delete An event is created when you delete an alert definition 
 sysdig-monitor.alert.list An event is created when you view the alerts in the monitoring instance 







 Captures: List of management events 



Table 2. Captures: List of activity tracker actions

 Action Description 

 sysdig-monitor.capture.create An event is created when you create a Monitoring capture 
 sysdig-monitor.capture.read An event is created when you load a Monitoring capture in the dashboard 
 sysdig-monitor.capture.update An event is created when you update a Monitoring capture 
 sysdig-monitor.capture.delete An event is created when you delete a Monitoring capture 







 Dashboards: List of management events 



Table 3. Dashboards: List of activity tracker actions

 Action Description 

 sysdig-monitor.dashboard.create An event is created when you create a dashboard
* [Sending email notifications to IBM Cloud Event Notifications](https://cloud.ibm.com/docs/monitoring?topic=monitoring-tutorial)
* [Sending SMS notifications to IBM Cloud Event Notifications](https://cloud.ibm.com/docs/monitoring?topic=monitoring-tutorial-en-sms)



For more information, see [Working with alerts and events](https://cloud.ibm.com/docs/monitoring?topic=monitoring-alerts).





 Data location 

Metric data is hosted on the IBM Cloud.



* Each multi-zone region (MZR) location collects and aggregates metrics for each instance of the IBM Cloud Monitoring that runs in that location.
* Data is colocated in the region where the IBM Cloud Monitoring instance is provisioned. For example, metric data for an instance that is provisioned in US South is hosted in the US South region.







 Data collection 

Monitoring agent data is collected at 10-seconds frequency.

Data that is published by platform metrics is collected on a 1-minute frequency.





 Data retention 

Data is retained for each instance based on a roll-up policy.

As time progresses, the data is rolled up from a fine granularity to a coarser one by the end 2 months.

The roll-up policy describes the granularity of the data over time:



* Data is retained at 10-second resolution for the first 4 hours.
* Data is retained at 1-minute resolution for 2 days.
* Data is retained at 10-minute resolution for 2 weeks.
* Data is retained at 1-hour resolution for 2 months.
* Data is retained at 1-day resolution for 15 months.
Monitoring cluster health 

Set up monitoring in IBM Cloud® Kubernetes Service to help you troubleshoot issues and improve the health and performance of your Kubernetes clusters and apps.

Continuous monitoring and logging is the key to detecting attacks on your cluster and troubleshooting issues as they arise. By continuously monitoring your cluster, you're able to better understand your cluster capacity and the availability of resources that are available to your app. With this insight, you can prepare to protect your apps against downtime.



 Choosing a monitoring solution 

Metrics help you monitor the health and performance of your clusters. You can use the standard Kubernetes and container runtime features to monitor the health of your clusters and apps.

Every Kubernetes master is continuously monitored by IBM. IBM Cloud Kubernetes Service automatically scans every node where the Kubernetes master is deployed for vulnerabilities that are found in Kubernetes and OS-specific security fixes. If vulnerabilities are found, IBM Cloud Kubernetes Service automatically applies fixes and resolves vulnerabilities on behalf of the user to ensure master node protection. You are responsible for monitoring and analyzing the logs for the rest of your cluster components.

To avoid conflicts when using metrics services, be sure that clusters across resource groups and regions have unique names.

IBM Cloud® Monitoring
: Gain operational visibility into the performance and health of your apps and your cluster by deploying a Monitoring agent to your worker nodes. The agent collects pod and cluster metrics, and sends these metrics to IBM Cloud Monitoring. For more information about IBM Cloud Monitoring, see the [service documentation](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started). To set up the Monitoring agent in your cluster, see [Viewing cluster and app metrics with IBM Cloud Monitoring](https://cloud.ibm.com/docs/containers?topic=containers-health-monitormonitoring).

Kubernetes dashboard
: The Kubernetes dashboard is an administrative web interface where you can review the health of your worker nodes, find Kubernetes resources, deploy containerized apps, and troubleshoot apps with logging and monitoring information.
actionStarted Boolean Whether the action was started during the same conversation turn. 
 actionTitle String The title of the action (for example, I want to pay my bill). 
 assistantId String The ID of the assistant. 
 browser String The browser that was used to send the message that triggered the action. 
 channel String The channel the customer used to send the message that started the action (for example, phone or chat). 
 device String The type of device that was used to send the message that triggered the action. 
 environment String The environment in which the action completed (such as draft or live.) 
 fallbackReason String The reason why the fallback action was called (for example, escalated to human agent or no action matches). 
 handler String The name of any handler that was called by the action. 
 language String The language of the assistant. 
 pageUrl String The URL of the web page from which the message that triggered the action was sent. 
 serviceInstance String The IBM Watson Assistant service instance. 
 sessionId String The ID of the session during which the message that started the action was sent. 
 skillsInvoked String[] An array of strings listing all skills that were invoked during handling of the message that started the action (for example, main skill or actions skill). 
 stepsVisited String[] An array of strings listing the steps visited during processing of the action. 
 subaction String The name of any other action that the action called during processing. 







 Session Started 

Sent when a new session is started.

Note: The v2 stateless API does not generate events for starting sessions.



 Property Type Description 

 accountId String The ID of the IBM account. 
 assistantId String The ID of the assistant. 
 browser String The browser that was used to send the message that started the session. 
 channel String The channel that started the session (for example, phone or chat). 
 device String The type of device that was used to send the message that started the session. 
 environment String The environment in which the session was started (such as draft or live.) 
 pageUrl String The URL of the web page from which the message that started the session was sent. 
 serviceInstance String The IBM Watson Assistant service instance.
When the upgrade is complete, the model resumes the status that it had before upgrade (ready or available). Checking the status of an upgrade operation is identical to checking the status of a training operation. For more information, see [Monitoring the train model request](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-acousticmonitorTraining-acoustic).

The service cannot accept requests to modify the model in any way until the upgrade request completes. However, you can continue to issue recognition requests with the existing version of the model during the upgrade.





 Upgrade failures 

The upgrade of a custom model fails to start if the service is handling another request for the model, such as a request to add data or a training request. The upgrade request also fails to start in the following cases:



* The custom model is in a state other than ready or available.
* The custom model contains no data (corpora, custom words, grammars, or audio resources).
* For a custom acoustic model that was trained with a custom language model, the custom models are based on different versions of the base model. You must upgrade the custom language model before upgrading the custom acoustic model. For more information, see [Upgrading a custom acoustic model](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-custom-upgradecustom-upgrade-acoustic).
IR-5 - Incident Monitoring 



  Control requirements 

IR-5 - 0
:   The organization tracks and documents information system security incidents.





  NIST supplemental guidance 

Documenting information system security incidents includes, for example, maintaining records about each incident, the status of the incident, and other pertinent information necessary for forensics, evaluating incident details, trends, and handling. Incident information can be obtained from a variety of sources including, for example, incident reports, incident response teams, audit monitoring, network monitoring, physical access monitoring, and user/administrator reports.