vania-janet/multiturn-rag-retrieval-data huggingface dataset:
To download the activity log, click the Download icon ![Download](https://cloud.ibm.com/docs-content/v1/content/icons/download.svg).







 Items and activity tracked 

For the early access release, here's the current list of items and activity that are tracked. Events are tracked if they complete successfully.



Items and activity

 Item Activity Notes 

 Assistant Created, Dialog activated, Dialog deactivated 
 Assistant Settings Updated 
 Action Created, Updated, Deleted <br><br> * Each save (auto or manual) is tracked as an update.<br> * Changes to action settings are tracked as an update.<br><br><br> 
 Variable Created, Updated, Deleted 
 Saved Response Type Created, Updated, Deleted 
 Version Created, Published, Deleted 
 Environment Created, Updated, Deleted 
 Intent Created, Updated, Deleted <br><br> * Each save (auto or manual) is tracked as an update.<br> * A renamed intent retains the old name in previous entries and won't have a link.<br><br><br> 
 Entity Created, Updated, Deleted <br><br> * Each save (auto or manual) is tracked as an update.<br> * A renamed entity retains the old name in previous entries and won't have a link.<br><br><br> 
 Dialog Node Created, Updated, Deleted Each save (auto or manual) is tracked as an update. 
 Search Updated 



If an item was triggered by the API, the activity log shows the account owner of the API key, even if the key is shared with another person who is triggered the event.



 What isn't included in the log 

These items aren't included in the activity log:



* Copying an action from another assistant
* Uploading actions, intents, entities aren't included as created
* Changing actions global settings
* Reverting a version to draft
* Adding or deleting entity values and synonyms
* Creating, updating, or deleting channel integrations
* Creating, updating, or deleting custom extensions
Step 5: Add a confirmation slot 

You might want to design your dialog to call an external reservation system and actually book a reservation for the user in the system. Before your application takes this action, you probably want to confirm with the user that the dialog has understood the details of the reservation correctly. You can do so by adding a confirmation slot to the node.



1. The confirmation slot will expect a Yes or No answer from the user. You must teach the dialog to be able to recognize a Yes or No intent in the user input first.
2. Click the Intents tab to return to the Intents page. Add the following intents and example utterances.





* yes

Yes
Sure
I'd like that
Please do
Yes please.
Ok
That sounds good.

![Shows the yes intent](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/slots-yes-intent.png)
* no

No
No thanks.
Please don't.
Please do not!
That's not what I want at all
Absolutely not.
No way

![Shows the no intent](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/slots-no-intent.png)





1. Return to the Dialog tab, and then click to edit the node with slots. Click Add slot to add a fourth slot, and then specify the following values for it:



Confirmation slot details

 Check for Save it as If not present, ask 

 `(#yes || #no) && slot_in_focus` $confirmation I'm going to reserve you a table for $guests on $date at $time. Should I go ahead? 



This condition checks for either answer.
message Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, assistant_id, Get the response to user input. 
 create-workspace Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, name, description, language, intents, entities, dialog_nodes, counterexamples, metadata, learning_opt_out Create a workspace. 
 delete-workspace Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id Delete a workspace. 
 get-workspace Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, export, include_audit Get information about a workspace. 
 list-workspaces Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, page_limit, include_count, sort, cursor, include_audit List workspaces. 
 update-workspace Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, name, description, language, intents, entities, dialog_nodes, counterexamples, metadata, learning_opt_out, append Update a workspace. 
 create-intent Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, intent, description, examples Create an intent.
update-workspace Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, name, description, language, intents, entities, dialog_nodes, counterexamples, metadata, learning_opt_out, append Update a workspace. 
 create-intent Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, intent, description, examples Create an intent. 
 delete-intent Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, intent Delete an intent. 
 get-intent Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, intent, export, include_audit Get information about an intent. 
 list-intents Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, export, page_limit, include_count, sort, cursor, include_audit List intents. 
 update-intent Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, intent, new_intent, new_description, new_examples Update an intent. 
 create-example Action username, password, iam_access_token, iam_apikey, iam_url, headers, headers[X-Watson-Learning-Opt-Out], url, workspace_id, intent, text Create a user input example.
catalog_integration.create creates a custom extension 
 catalog_integration.delete deletes a custom extension 
 catalog_integration.update updates a custom extension 
 counterexample.create marks test user input in the "Try it out" pane as being irrelevant or corrects the categorization of a user input that was incorrectly assigned to an intent by marking it as irrelevant 
 counterexample.delete deletes a counterexample 
 counterexample.update edits a counterexample 
 data.delete deletes multiple training data items, such as multiple entities or intents 
 data.update does a bulk action, such as importing a CSV file of intents or entities to the skill 
 data_type.create creates a saved response 
 data_type.delete deletes a saved response 
 data_type.update updates a saved response 
 entity.create creates an entity 
 entity.delete deletes an entity 
 entity.update edits an entity 
 environment.create adds an environment 
 environment.delete deletes an environment 
 environment.updates updates an environment 
 example.create adds a user input example to an intent 
 example.delete deletes a user example from an intent 
 example.update edits a user example that is associated with an intent 
 integration_defintion.create creates an integration 
 integration_defintion.delete deletes an integration 
 integration_defintion.update updates an integration 
 intent.create creates an intent 
 intent.delete deletes an intent 
 intent.update edits an intent 
 log.create corrects an intent that was inaccurately categorized by the skill from the Analytics>User conversations page 
 node.create creates a dialog node 
 node.delete deletes a dialog node 
 node.update edits a dialog node 
 notifier.create creates a notifier 
 notifier.delete deletes a notifier 
 notifier.update updates a notifier 
 processor.create creates a processor 
 processor.delete deletes a processor 
 processor.update updates a processor 
 recommendationfile.create uploads a CSV file of utterances to a skill from which Watson can derive intent recommendations
Global load balancer concepts 

This document contains some concepts and definitions related to the global load balancer and how it affects your IBM Cloud® Internet Services deployment.



 Global load balancer 

A global load balancer manages traffic across server resources located in multiple regions. The origin server can serve up all of the content for a website, provided that the web traffic does not extend beyond the server's processing capabilities and latency is not a primary concern. A global load balancer manages a pool implementation that allows for the traffic to be distributed to multiple origins. This pool capability provides many benefits including:



* Minimizes response time
* Creates higher availability through redundancy
* Maximizes traffic throughput



A global load balancer routes traffic to the pool with the highest priority, distributing the load among its origin servers. See the following Pool section for how traffic is distributed within a pool. If the primary pool becomes unavailable, traffic is routed automatically to the next pool in the list based on priority.

If pools are set up for specific regions, traffic from those regions is sent to the pools for the specified region first. Traffic falls back to the default pools only when all pools for a given region are down. In this case the fallback pool is the pool with the lowest priority.



 How it works 

When a global load balancer is created, a DNS record is automatically added for it with the name of the load balancer. The load balancer then returns one of the origin IP addresses to a client making a DNS request.

For example, an origin pool is created with two origins identifying IP addresses 169.61.244.18 and 169.61.244.19. If a global load balancer is created with the name glbcust.ibmmo.com using the origin pool, then a client on the internet can execute the command:

$ ping glbcust.ibmmo.com
PING glbcust.ibmmo.com (169.61.244.18): 56 data bytes

In this example, CIS:



* Created a DNS record named glbcust.ibmmo.com.
* Used the global load balancer to resolve the DNS name to one of the IP addresses identified in the origin pool.
On this page[For my CDN, what is the difference between HTTPS with a Wildcard certificate and HTTPS with SAN certificate?](https://cloud.ibm.com/docs/CDN?topic=CDN-faq-for-httpsfor-my-cdn-what-is-the-difference-between-https-with-wildcard-certificate-and-https-with-san-certificate)[How is Domain Validation with redirect accomplished?](https://cloud.ibm.com/docs/CDN?topic=CDN-faq-for-httpshow-is-domain-validation-with-redirect-accomplished)[How long does Domain Validation take?](https://cloud.ibm.com/docs/CDN?topic=CDN-faq-for-httpshow-long-does-domain-validation-take)[How long does it take to create and enable HTTPS for my CDN with a DV SAN certificate?](https://cloud.ibm.com/docs/CDN?topic=CDN-faq-for-httpshow-long-does-it-take-to-create-and-enable-https-for-my-cdn-with-a-dv-san-certificate)[How long does it take to delete a CDN with a DV SAN certificate?](https://cloud.ibm.com/docs/CDN?topic=CDN-faq-for-httpshow-long-does-it-take-to-delete-a-cdn-with-a-dv-san-certificate)[Is there any additional cost associated with using a DV SAN certificate for my CDN?](https://cloud.ibm.com/docs/CDN?topic=CDN-faq-for-httpsis-there-any-additional-cost-associated-with-using-a-dv-san-certificate-for-my-cdn)[Can my CDN created using HTTPS with Wildcard be updated to use a DV SAN certificate?]
Why is my account inactive? 

You can't create an app in IBM Cloud if your account is inactive. You must contact the support team to fix this problem.

  What’s happening 

When you try to create an app in IBM Cloud, the following error message is displayed:

> BXNUI0096E: The app wasn't created. Your account is inactive because it was canceled or suspended.

  Why it’s happening 

Your account becomes inactive when it is canceled or suspended.

  How to fix it 

Make sure you have selected the correct account in the IBM Cloud console. You can [switch accounts](https://cloud.ibm.com/docs/account?topic=account-accountfaqs&locale=dkswitch-between-accounts) if needed. Check with the account owner to make sure you are invited to the account with the appropriate access. To reactivate your account, contact IBM Cloud Support by calling 1 (866) 325-0045 and selecting option 3. Include the following information so the support team can help restore the correct account:



*  The IBMid that you use to log in to IBM Cloud.
*  The name of the organization in which your app is being created. This information can help the support team determine whether you're assigned the correct roles or membership in your organization.
Why does an associated reserved IP address show 0.0.0.0? 

Reserved IP addresses belong to a subnet. You can create these IP addresses explicitly by using subnet APIs (POST /subnets/{subnet_id}/reserved_ips), or implicitly as part of an endpoint gateway call by specifying the subnet.

  What’s happening 

Reserved IP address shows an 0.0.0.0 address.

  Why it’s happening 

The allocation of the reserved IP address is completed in the background after the call is made. The value of the IP address shows 0.0.0.0 until the allocation of the IP address is complete, which can take up to 30 seconds.

  How to fix it 

If the IP address is not allocated within this timeframe, try the following steps:



1.  Detach the reserved IP address from the endpoint gateway and retry the process.
2.  If reattaching does not work, try to create a reserved IP address on its own as a subnet operation. If the reserved IP address is created, you can attempt to create the endpoint gateway by using the explicitly created reserved IP address.
The evidence format contains the result of the task (passing or failing), links to the created artifacts, and links to any incident issue that is created based on the Task result.

These tools focus only on evidence collection and do not change the behavior of your build process. The DevSecOps reference pipeline does not break due to failed Task results. An image can be built and deployed with failing tests and vulnerabilities if evidence of the checks and failures exists, the team is notified, a change request that is created during the deployment shows evidence of these issues, and the change request is manually approved.





 Evidence flow 

The following diagram shows how the evidence is handled and how it flows through the stages of continuous integration and continuous deployment.

Zoom

![Evidence flow](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/evidence-flow.png)

Figure 2. Evidence flow

Each piece of evidence that is collected in the various stages of the DevOps Architecture is stored in auditable evidence lockers. During deployment, this evidence is collected to create an evidence summary that is saved to the evidence locker at the end of the deployment run.

The evidence summary is attached to the change request, which is posted to the change request store. During a manual change request approval, the approver is aware of any issues that are found during the build. Additionally, the summary is submitted to the Security and Compliance Center.





 v2 evidence (current format) 



 v2 evidence locker 

As opposed to v1 version, evidence is stored in a flat hierarchy, where each piece of evidence is identified by its own SHA256 hash, this provides a layer of integrity protection (that is, any modification of the evidence content can be detected). As each piece of evidence is related to one or more assets, the evidence summarization algorithms discover the relevant evidence based on assets (as opposed to pipeline-run IDs in v1 evidence lockers).

The only hierarchy is the type differentiation and some hash grouping similar to the structure of Git hash objects.



 Example 

.
└── raw/
router-default LoadBalancer 172.21.47.119 169.XX.XX.XX 80:32637/TCP,443:31719/TCP 26m
router-dal12 LoadBalancer 172.21.47.119 169.XX.XX.XX 80:32637/TCP,443:31719/TCP 26m
router-internal-default ClusterIP 172.21.51.30 <none> 80/TCP,443/TCP,1936/TCP 26m



 Why it’s happening 

Router services might not deploy for one of the following reasons:



* If no Ingress controller services are deployed or Ingress controller services are not assigned an external IP address: In standard clusters, the first time that you create a cluster in a zone, a public VLAN and a private VLAN in that zone are automatically provisioned for you in your IBM Cloud infrastructure account. In that zone, 1 public portable subnet is requested on the public VLAN that you specify and 1 private portable subnet is requested on the private VLAN that you specify. For Red Hat OpenShift on IBM Cloud, VLANs have a limit of 40 subnets. If the cluster's VLAN in a zone already reached that limit, the Ingress Subdomain fails to provision and the default public Ingress controller for the Ingress controller fails to provision. To view how many subnets a VLAN has, from the [IBM Cloud infrastructure console](https://cloud.ibm.com/classic?), select Network > IP Management > VLANs. Click the VLAN Number of the VLAN that you used to create your cluster. Review the Subnets section to see whether 40 or more subnets exist.
* If one zone has no Ingress controller service: When your Ingress controller services are created, they are automatically spread across the zones in your cluster. If the network for the first zone that your cluster was created with is not ready when the Ingress controller services are created, the Ingress controller service for that zone might be placed in a different zone. Two Ingress controller services might be created in one zone, and no Ingress controller service is created in the initial zone.



 How to fix it
Activity Tracker events 

Use the IBM Cloud® Activity Tracker service to track how users and applications interact with the Event Streams service on the Standard and Enterprise plans in IBM Cloud®.

The IBM Cloud Activity Tracker service records user-initiated activities that change the state of a service in IBM Cloud. For more information, see the [Activity Tracker](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started).

Events are formatted according to the Cloud Auditing Data Federation (CADF) standard, further details of the information they include can be found [here](https://cloud.ibm.com/docs/Activity-Tracker-with-LogDNA?topic=Activity-Tracker-with-LogDNA-event).



 Topic events 

Event Streams instances that are on the Enterprise plan or the Standard plan automatically generate topic events.

The following table lists the topic events:



Table 1. Event Streams topic events

 Action Description 

 event-streams.topic.create An event is created when you create a topic. 
 event-streams.topic.delete An event is created when you delete a topic. 
 event-streams.topic.update An event is created when you update a topic's configuration or increase partitions. 



Additional information about topic configuration is logged in the update and delete events, for example partitions, retentionMs, and segmentMs.





 Message audit events 

You can enable message audit events on a per topic basis for Event Streams instances that are on the Enterprise plan. Also, see [How to enable message audit events](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-at_eventsenable-message-events).

The following table lists the message audit events:



Table 2. Event Streams message events

 Action Description 

 event-streams.message.read An event is created when message audit is enabled on a topic and a consumer is reading data from the topic. 
 event-streams.message.write An event is created when message audit is enabled on a topic and a producer is writing data to the topic. 
 event-streams.message.delete An event is created when message audit is enabled on a topic and records are deleted from the topic.
Activity Tracker events 

Use the IBM Cloud® Activity Tracker service to track how users and applications interact with the IBM MQ on Cloud service on the Default and Custom plans in IBM Cloud®.

The IBM Cloud Activity Tracker service records user-initiated activities that change the state of a service in IBM Cloud. For more information, see the [Activity Tracker ![External link icon](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/icons/launch-glyph.svg)](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started).



 List of events 

IBM MQ on Cloud service instances on the Default and Custom plans automatically generate events so that you can track activity on your service.



Table 1. IBM MQ on Cloud events

 Action Description 

 mqcloud.queue-manager.create An event is created when you create a queue manager 
 mqcloud.queue-manager.delete An event is created when you delete a queue manager 
 mqcloud.queue-manager.update An event is created when you update a queue manager 
 mqcloud.key-store-cert.create An event is created when you import a certificate into a key store 
 mqcloud.key-store-cert.delete An event is created when you delete a certificate from a key store 
 mqcloud.key-store-cert.update An event is created when you update a certificate in a key store 
 mqcloud.trust-store-cert.create An event is created when you import a certificate into a trust store 
 mqcloud.trust-store-cert.delete An event is created when you delete a certificate from a trust store 
 mqcloud.trust-store-cert.update An event is created when you update a certificate in a trust store 
 mqcloud.admin-credentials.create An event is created when you create administrator credentials
The CNAME, including the IBM suffix .cdn.appdomain.cloud., must be used for access to the service. For example, https://www.example-cname.cdn.appdomain.cloud

In the case of SAN certificate, multiple customer domains share a single SAN certificate by adding their domain names into the SAN entries. The service can then be accesses using the hostname, for instance https://www.example.com
* How is Domain Validation with redirect accomplished?

It depends on your server. The procedure for completing Domain Validation for Apache and Nginx servers can be found on the [Completing Domain Control Validation for HTTPS](https://cloud.ibm.com/docs/CDN?topic=CDN-completing-domain-control-validation-for-https-with-dv-sanredirect) page.
* How long does Domain Validation take?

Domain Validation normally takes 2 - 4 hours, but it varies depending on the method that is chosen for validation. DV with CNAME validation is the fastest, typically taking under an hour. DV using the Standard and Redirect methods typically take 4 hours after the challenge has been addressed.
* How long does it take to create and enable HTTPS for my CDN with a DV SAN certificate?

A normal request to enable HTTPS takes an average of 3 - 9 hours, from the initial request to running.
* How long does it take to delete a CDN with a DV SAN certificate?

Deleting your CDN requires that your domain be removed from the certificate on all of the Edge servers. This process can take up to 8 hours to complete.
* Is there any additional cost associated with using a DV SAN certificate for my CDN?

No. DV SAN certificate configurations are provided to you at no additional charge that is compared with HTTP or HTTPS with a Wildcard certificate.
* Can my CDN created using HTTPS with Wildcard be updated to use a DV SAN certificate?

No, a wildcard mapping cannot be changed to SAN certificate.
* What is a certificate authority?

A certificate authority (CA) is an entity that issues digital certificates.