vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Create an Event Notifications subscription 

Create an Event Notifications subscription. Destinations subscribe to topics. Multiple destinations can subscribe to a single topic. An email subscription is a list of all emails IDs, and an SMS subscription is a list of all phone numbers that a notification is routed to. A webhook subscription links a webhook destination to a topic.

Of these, IBM Cloud Email service and IBM Cloud SMS service are supported out-of-the box.



 Step 1: Create a subscription 

Click Subscriptions in the Event Notifications console.





 Step 2: Add subscription details 



* Click Create to display subscription side panel.
* Complete the following subscription details:



* Name: name of the subscription.
* Description: add an optional description.



* Select a Topic from the list.
* Select a Destination type from the Destination list.



* IBM Cloud SMS service - When you select this option, you can add up to 3 phone numbers for lite plan and 100 phone numbers for standard plan to the recipient list. After adding phone number and when you click Create subscription, the number are added to the Invited tab. The Active tab, displays the phone number of recipients who confirmed receiving SMS notifications for the topic selected in the invite.



* When a recipient clicks the Unsubscribe link, the recipients number is moved to the Unsubscribed tab. To restart the subscription, the recipient need to contact IBM Event Notifications service administrator to add the number back to subscription.
* In some cases, the carrier service allows keywords like START and STOP. When a recipient sends a response STOP, sending notifications to the recipient gets immediately disabled. However, the phone number is moved to Unsubscribed tab only on the next attempt to send an SMS to the same number. The recipient can restart to receive the SMS by sending a response code START in some case where keyword use is permitted by the carrier service.



* IBM Cloud Email service - When you select this option, you can add up to 100 email addresses of the recipient list. The Invited tab displays the list of users who not yet accepted the invitation to be a subscriber. The Active tab displays the list of recipients email addresses and the date activated.
BR-SAO https://br-sao.monitoring.cloud.ibm.com 163.107.66.98 <br>163.109.67.242 <br>169.57.141.43 https (TLS) 443 







 Subnets for webhook notifications from IBM Cloud Monitoring 

To receive alert notifications using webhooks from the IBM Cloud Monitoring service, you may need to define firewall rules for the subnets that are invoking your webhooks.



Table 4. Source Subnets for Webhook notifications from IBM Cloud Monitoring

 Region Alert Notification Source Subnets 

 US-SOUTH 150.239.180.0/25 <br>169.46.0.64/29 <br>169.46.39.48/28 <br>169.46.58.24/29 <br>169.47.115.192/28 <br>169.47.71.24/29 <br>169.48.214.64/29 <br>169.48.235.16/28 <br>169.60.151.168/29 <br>169.62.221.32/28 <br>174.36.68.96/27 <br>50.22.148.64/26 <br>52.116.222.192/27 <br>52.117.187.192/27 <br>52.118.158.0/25 <br>52.118.7.64/26 <br>67.228.207.64/26 <br>67.228.219.0/25 
 EU-DE 149.81.151.128/27 <br>149.81.201.192/26 <br>149.81.77.72/29 <br>149.81.99.192/28 <br>158.177.44.192/26 <br>159.122.102.32/29 <br>161.156.1.224/27 <br>161.156.102.200/29 <br>161.156.69.144/28 <br>161.156.77.64/26 <br>169.50.36.64/27 <br>169.50.9.0/28
* UI
* API







 Enabling event notifications for projects 

As an administrator of projects, you might want to send notifications of events in projects to other users, or human destinations, by using email, SMS, or other supported delivery channels. You might want to send these notifications of events to other applications to build logic by using event-driven programming by using webhooks, for example. This is made possible by the integration between projects and IBM Cloud® Event Notifications.

To send information to Event Notifications, you must connect your projects instance to Event Notifications. For more information about working with Event Notifications, see [Getting started with Event Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-getting-started).



 How events are collected and sent by projects 

When an event of interest takes place in your project instance, projects communicate with a connected Event Notifications instance to forward a notification to a [supported destination](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destination). Events are generated based on actions that users take within the project. For example, if the validation of a configuration is successful, an event is generated to notify users of this action.





 Events for projects 

The following table lists the projects events.



Table 1. Actions that generate event notifications in projects

 Event type Description 

 check.pipeline.failed Changes failed validation. An event is generated when a validation fails. 
 config.install-job.failed Changes failed to deploy. An event is generated when an architecture deployment fails. 
 config.uninstall-job.failed Destroy resources failed. An event is generated when the action to destroy configuration resources fails. 
 check.pipeline.ready Changes require approval. An event is generated when the latest changes require approval. 
 config.version.available A version update is available. An event is generated when a new version of a deployable architecture is available. 
 config.defn.updated Changes are ready to deploy. An event is generated when a configuration is updated in the project.
<-- <section "id="section-update-alert-webhook-options" "> --> Command options WEBHOOK_ID: The ID of alert webhook. Required.--name: The name of the webhook.--url: The POST endpoint to call when dispatching an alert.--secret: The secret that will be passed in the webhook auth header when dispatching a webhook alert.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-alert-webhook-options" "> --><-- <section "id="section-update-alert-webhook-examples" "> --> Examples Update an alert webhook b2633e68-9a64-4519-b361-a64a67c8db8e. ibmcloud cis alert-webhook-update b2633e68-9a64-4519-b361-a64a67c8db8e --name testwebhook --url https://hooks.slack.com/services/Ds3fdBFbV/1234568 -i "cis-demo"
<-- </section "id="section-update-alert-webhook-examples" "> --><-- </section "id="section-update-alert-webhook" "> --><-- <section "id="section-delete-alert-webhook" "> --> ibmcloud cis alert-webhook-delete Delete an alert webhook. ibmcloud cis alert-webhook-delete WEBHOOK_ID -i, --instance INSTANCE] -f, --force] ! ! ! ! ! ! ! ! ! ! ! !
Detecting trigger words 

Use the Trigger word detected action to add words or phrases to two separate groups. The first group connects customers with an agent. The second group shows customers a customizable warning message.

By default, this action has two steps—the Connect to agent step and the Show warning step. To see how this action works, click Set by assistant in the list of actions, and then click Trigger word detected.

This is a beta feature that is available for evaluation and testing purposes.



 Connect to agent 

The first step of the Trigger word detected action is the Connect to agent step. The Connect to agent step goes to the Fallback action if any trigger words are detected in the customer's input. Use this step to capture any key phrases where it’s important to connect a customer with a live agent rather than activate any further actions.

For example, you might add hurt and harm as trigger words for the Connect to agent step:

Zoom

![Adding trigger words to the Connect to agent step](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/connect-to-agent-phrases.png)

Adding trigger words to the Connect to agent step

In this example, a customer enters a word or phrase including hurt or harm, which triggers the Fallback action. Step 4 has:



* Danger word detected as the fallback reason.
* The default message: It seems this conversation would be best managed by a human agent. Let me connect you to one of our agents. You can customize this message.
* And then set to Connect to agent (action ends).



For more information about the Fallback action, see [Editing the fallback action](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-handle-errorsfallback-action).





 Show warning 

The second and final step of the Trigger word detected action is the Show warning step. The Show warning step shows a customizable warning message to your customer if any trigger words are detected in the customer's input.
[Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Archiving of events ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker/images/checkmark-icon.svg) 
 Multi-channel Alerting !
Create and send push notifications to iOS mobile using Event Notifications 

Create an Event Notifications service, add a push destination for Apple Push Notification service (APNs), and send messages to iOS devices.



 What is Event Notifications? 

Event Notifications is an event notification routing service that notifies you of critical events that occur in your IBM Cloud account or triggers automated actions by using webhooks. You can filter and route event notifications from IBM Cloud services like Availability Monitoring, to email, SMS, push notifications (FCM or APNs), and webhooks.





 How do clients use iOS Push Notifications? 

The following diagram shows you how clients use iOS Push Notifications.

Zoom

![How clients use push notifications](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-how-send-apns.svg)

Figure 1. How clients use push notifications





 Objectives 

This tutorial shows you how to send push notifications as follows:



* Create a mobile app with Event Notifications.
* Get APNs credentials.
* Download the code and complete the notifications setup.
* Configure and send iOS Push Notifications to a mobile device.







 Before you begin 

You must have the following prerequisites in place:



* An IBM Cloud account. If you do not have one, [create an IBM Cloud account](https://cloud.ibm.com/).
* An Event Notifications instance.
* An IAM API key to allow the SDK to access your account. Create one [here](https://cloud.ibm.com/iam/apikeys).
* Xcode 9.3+
* Swift 4.2+
* iOS 10.0+







 Step 1: Create an Event Notifications service instance 



* Log in to your [IBM Cloud account](https://cloud.ibm.com/).
,"payload_type": "test","reported_by": {"id": "compliance","title": "IBM Cloud Security and Compliance Center", "url": "https://cloud.ibm.com/security-compliance"},"severity": "LOW","short_description": "Success Your Event Notifications instance is configured with IBM Cloud Security and Compliance Center.","transaction_id":"6a25fd3d-8530-43b9-96a5-ede2a7712bc9"}
Show more
* The following example shows the target device configuration example.

{"fcm_devices": "deviceidstring"],"user_ids": "useridstring"], "platforms": "G"]!!!!!!}
* The following example shows the send notification general payload for cli version above 0.1.1
For example, you can name the view Upload Frankfurt to indicate archive files into the bucket from an IBM Log Analysis instance located in Frankfurt.

The data that is displayed through the view reports write actions of archive files to the archive bucket.







 Step 3. Define an alert to notify the absence of new archive files 

Complete the following steps to define an absence alert that notifies you when archiving is not happening:



1. Select the view name.

![Select view name](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/archive-view-2.png)
2. Select Attach an alert. The following page opens.

![Select alert type](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/archive-view-3.png)
3. Select View-specific alert.
4. Choose the notification channel.
5. Configure an Absence alert.

![Sample absence alert](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/archive-view-3.png)

Archiving is configured hourly. Consider configuring the absence alert over a period of 24 hours to monitor archiving daily.



For more details on how to configure an alert, see [Creating alerts](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-create_alert_ui).







 Configure an alert to detect unauthorize access to the bucket
By default, three types of logs are automatically generated for your Satellite location: [R00XX-level error messages](https://cloud.ibm.com/docs/satellite?topic=satellite-healthlogs-error), [the status of whether resource deployment to the location is enabled](https://cloud.ibm.com/docs/satellite?topic=satellite-healthlogs-deploy), and [the status of Satellite Link](https://cloud.ibm.com/docs/satellite?topic=satellite-healthlogs-link). Review the following sections for an example of each log type and descriptions of each log field.





 How can I set up alerts for location error logs? 

You can use the built-in Log Analysis dashboard tools to save log searches and set up alerts for certain types of logs, such as errors.



1. To filter for a specific Satellite location, click Apps in the Filters toolbar, select the CRN for your Satellite location, and click Apply. To identify the CRN for your location, look for the location's ID at the end of the CRN.
2. Search for a specific query that you want an alert for. For example, to be alerted for any logs that contain R00XX-level location error messages, search for R00. To be alerted for Satellite Link health check failures, search for Failed to reach endpoint.
3. Click Unsaved view > Save as new view. Add a name and an optional category.
4. In the Alert drop-down list, select View-specific alert and follow the steps for the notification channel that you selected to configure a custom alert for this log query.
5. Click Save view.







 Is IBM alerted for any of these logs? 

The IBM Cloud Monitoring component generates certain alerts for issues with your location setup and host infrastructure. To review the alerts that IBM monitors, see [IBM monitoring to resolve and report location alerts](https://cloud.ibm.com/docs/satellite?topic=satellite-monitormonitoring-default).







 R00XX error logs
FAQs for Event Notifications 

FAQs for Event Notifications provide answers to common operations issues.



 Why are messages reported as delivered but not received by the user? 

Sometimes messages are reported as delivered but are not received by the user for the following reasons:



* They are rejected by the telecom operator. If the same message is repeated over a span of time, messages are classified as SPAM message by the operator.



A resolution is to add any TransactionID or ReferenceID to the message body. These IDs classify the SMS as transactional, and is not blocked by the operator.



* The user opts out. If the user opts out from messaging by sending opt-out text like Opt Out, Stop, or Exit, then messages do not reach that user and the status report states that. The user can send an Opt in message to the same source to restart receiving messages.







 Why do some devices are marked invalid and deleted from database? 

Sometimes the devices are marked invalid and deleted from database, if they meet these invalid conditions:



* FCM or Android devices:



* invalidRegistration - might be due to incorrect registration token format passed to the server.
* MismatchSenderID - a mismatch in the senderID who is not part of the user group that is tied to a registration token.
* NotRegistered - an invalid registration token due to various reasons (like client app getting unregistered with FCM, tokens are invalid, registration token expires, client app that is updated but the new version that is not configured to receive messages).



For more information, see [FCM error response codes for downstream messages](https://firebase.google.com/docs/cloud-messaging/http-server-referror-codes).
* APNS or Safari devices:



* Unregistered - the device token is not active for the specified topic.
* BadDeviceToken - the specified device token is invalid.
* DeviceTokenNotForTopic - the device token doesn’t match the specified topic (bundle ID).
Phrases that are too short or too long are usually not effective as example training phrases for your assistant.
* The unrecognized requests are compared to the latest version of your actions so that requests that would no longer be unrecognized with your latest actions version are filtered out.
* Groups for which the request count is less than 10 are excluded. But if this might result in less than 5 groups, the algorithm tries to produce groups that include more than 5 request counts until a total of 5 groups are produced.
* If you have a small volume of data, the algorithm allows examples closer to the existing training data for grouping.



As a result of the algorithm:



* A list of groups might not always appear
* The groups might not include all unrecognized requests that you see on the Conversations page



Several events cause your groups to be refreshed by using the latest data:



* The first time that you visit the Recognition page for a specific environment, Watson Assistant generates groups
* If it has been at least 1 day since the groups were last generated, or if you edit your actions in your draft environment, the groups are refreshed when you return to the Recognition page
* You can refresh the groups by using the Refresh icon ![Refresh](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/renew.svg)



This table explains the details of the list of groups:



Unrecognized request groups list

 Column Description 

 Group A name is generated based on the example phrases in the requests. 
 Examples Some of the unrecognized requests are shown as a preview. 
 Request count The number of unrecognized requests in the group. Focus on groups with a higher count of unrecognized requests. 
 Percentage The percentage of unrecognized requests relative to the other groups. Focus on groups with a higher percentage of unrecognized requests. 







 Creating actions from unrecognized requests 

To create actions based on unrecognized requests:



1.
Set the Enable disambiguation switch to Off.
4. Click Save, and then click Close.
5. Publish a new version of your assistant to the live environment to disable clarification. For more information, see [Publishing your content](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-publish).







 Excluding an action from clarifying questions 

You can also prevent a single action from being used in a clarifying question. The effect of this choice depends on the confidence score for the action that you exclude.

If the action has the highest confidence score for a customer's question, no clarifying question is asked, and the action is triggered.

If the action doesn't have the highest confidence score, the action is excluded from the list of choices in the clarifying question.

For more information about confidence scores, see [Confidence scoring](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-understand-questionsunderstand-questions-confidence-scoring).

To exclude an action from clarification:



1. From the action editor, click the Action settings icon ![Gear icon](https://cloud.ibm.com/docs-content/v1/content/icons/settings.svg).
2. In Action Settings, toggle the Ask clarifying question switch to Off.









 Coordinating how multiple actions start 

As you work on your assistant, it's a good idea to coordinate customer phrase examples across multiple actions. It's important to distinguish how each action is triggered. When a user enters a question or request, the phrase is evaluated across all the Customer starts with examples in every action. If two actions have similar phrase examples, then the wrong action might get triggered by your user's question.



 Confidence scoring 

Behind the scenes, Watson Assistant determines a confidence score for each phrase. The score is absolute, meaning that a confidence score is assigned based on a predetermined scale, and not relative to other customer phrases. This approach adds flexibility in case multiple questions or requests are detected in a single user input.
[2021-08-15](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-aug1521) Classifications GA and Categories type system Version 2 features. 
 [2021-03-25](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-mar2521) Custom categories (beta) and custom classifications (beta) features. 
 [2020-12-09](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-dec0920) Version 2 English entity type system. 
 [2020-12-02](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-dec0220) Version 2 Korean entity type system.<br><br>Version 2 Spanish entity type system. 
 [2020-08-01](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-aug0120) Taxonomy changes aimed towards standardization of the label names in the default taxonomy. 
 [2019-07-12](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-jul1219) New English entities model with improved accuracy and confidence scores. 
 [2019-06-04](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-jun0419) Fixed a bug that caused entities requests with custom models to ignore the limit option.<br><br>The default limit value for all entities requests is now 50 for all models.<br><br>The maximum limit value of 250 entities has been removed.