vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Route filtering examples 



 How filters are matched 

To describe how filters are matched, consider the following gateway setup:



* default_import_route_filter: permit
* import_route_filters



* 1 - permit 10.10.0.0/19
* 2 - deny 10.10.0.0/16 ge 18 le 30
* 3 - deny 120.120.154.0/24



* default_export_route_filter: deny
* export_route_filters



* permit 10.10.0.0/18







 Importing routes 

For this example, routes from the customer on-premises network pass through the import_route_filters to determine whether the direct link learns them or not. Let's first understand the route filters:

Route filter 1
Action: permit
Address: 10.10.0.0
Mask length: 19
Minimum matching length (ge): 19
Maximum matching length (le): 19

Route filter 2
Action: deny
Address 10.10.0.0
Mask length: 16
Minimum matching length (ge): 18
Maximum matching length (le): 30

Route filter 3
Action: deny
Address 120.120.154.0
Mask length: 24
Minimum matching length (ge): 24
Maximum matching length (le): 24

Consider an on-premises network connected to a direct link with the following routes:



* Route 1 - 10.10.0.0/16
* Route 2 - 10.10.0.0/18
* Route 3 - 10.10.0.0/19
* Route 4 - 120.120.154.0/24
* Route 5 - 10.10.128.0/18



Only Route 1 - 10.10.0.0/16 and Route 3 - 10.10.0.0/19 would be learned by the direct link and advertised to attached virtual connections.



* Route 1 - 10.10.0.0/16 does not match with any import filter.



* The route matches filter 2 by address and mask length, but the ge option changes the prefix match specification, excluding route 1's mask of /16.
* [ibmcloud oc logging filter get](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_log_filter_view)
* [ibmcloud oc logging filter rm](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_log_filter_delete)
* [ibmcloud oc logging filter update](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_log_filter_update)



* [ibmcloud oc logging refresh](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_logging_refresh)







 ibmcloud oc nlb-dns 

[Create and manage host names for network load balancer (NLB) IP addresses in a cluster and health check monitors for host names](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clinlb-dns).



* [ibmcloud oc nlb-dns add](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_nlb-dns-add)
* nlb-dns create: Create a DNS host name.



* [ibmcloud oc nlb-dns create classic](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_nlb-dns-create)
* [ibmcloud oc nlb-dns create vpc-gen2](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_nlb-dns-create-vpc-gen2)
When you create a PagerDuty notification channel, consider the following information:



* You must manually configure the integration with PagerDuty.
* You must provide the PagerDuty API key.



After you create a view, check the view in the UI.



1. Refresh the browser to see the view listed in the Views section.
2. Select the view to display it.
3. Check the data that is available through the view is the one that you expect.



* If you do not see any data, check that data is being generated for the auditing events that you are planning to monitor through this view. For example, you can check the Everything view and look for events.
* If data is being generated, and you still cannot see any data, check the body parameter values that you have defined for the view. One of them might be set to the wrong value and the search criteria does not find any matching events.





If you try to create a view without defining a category, you get the following error message:

{"details":[{"message":""category0]" is not allowed to be empty","key":"category0]"}],"error":""category[0]" is not allowed to be empty","code":"BadRequest","status":"error"}

If you try to create a view without a valid category, you get the following error message:

{"error":"Invalid category name(s): CATEGORYNAME","code":"BadRequest","status":"error"}

If you try to define a view and you do not define any of the following body parameters, query, hosts, apps, levels, tags, you can get the following error:

{"details":[{"message":""value" must contain at least one of query, hosts, apps, levels, tags]","key":"value"}],"error":""value" must contain at least one of [query, hosts, apps, levels, tags]","code":"BadRequest","status":"error"}





 Getting views
Check for @animal, then save it as $animal.

And to deal with a possible cat response, add this value to the Found condition:

If @animal:cat then, "I'm sorry. We do not groom cats."

In the JSON editor for the Found condition, reset the value of the $animal context variable because it is currently set to cat and should not be.

{
"output":{
"text": {
"values": [
"I'm sorry. We do not groom cats."
]
}
},
"context":{
"animal": null
}
}







 Slots examples 

To access JSON files that implement different common slot usage scenarios, go to the community [conversation repo](https://github.com/watson-developer-cloud/community/tree/master/watson-assistant) in GitHub.

To explore an example, download one of the example JSON files, and then import it as a new dialog skill. From the Dialog tab, you can review the dialog nodes to see how slots were implemented to address different use cases.
If set to true, the filter defaults to include the entire public catalog, and subsequent filters are excluded. If set to false, the filter excludes the entire public catalog, and subsequent flags are included. For more information, see [Managing catalog settings](https://cloud.ibm.com/docs/account?topic=account-filter-account).

--offering-format FORMAT (optional)

--category CATEGORY (optional)
: Provide the category that best fits how users might use your product. Categories are used to organize products in the catalog based on common solutions, function, or use. You can select only one category. Run the ibmcloud catalog offering category-options command to view all options. Default is Developer tools.

--compliance TYPE (optional)
: Provide a comma-separated list of compliance categories that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--deployment-target TARGET (optional)
: Provide a comma-separated list of deployment targets that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--exclude-list LIST (optional)
: Provide a comma-separated list of product IDs or names that must be excluded in the filtered public catalog.

--include-list LIST (optional)
: Provide a comma-separated list of product IDs or names that must be included in the filtered public catalog.
: Provide a comma-separated list of product formats that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--pricing-plan PLAN (options)
: Provide a comma-separated list of pricing plans that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--provider PROVIDER (optional)
: Provide a comma-separated list of providers that you want to include or exclude. Run the ibmcloud catalog filter options command to view all options.

--release RELEASE (optional)
: Provide a comma-separated list of categories that you want to include or exclude.
When you exclude logs through an exclusion rule, you can choose to Preserve these lines for live-tail and alerting. When you check this option, log lines that match the exclusion rule are shown through the live tail and you can set up an alert for that data.

[Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-exclusion_rules).





 Configuring the usage alert 

In a IBM Log Analysis instance, you can define an alert to notify when the data usage in the instance reaches the data usage threshold that you set for the instance.

Complete the following steps to configure an alert that informs you when you reach a specific data volume in the instance:



1. [Launch the IBM Log Analysis web UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-view_logsview_logs_step2).
2. Click the Usage icon ![Usage icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/usage.png).

In the Dashboard section, you can see your data usage.
3. Define a Usage Alert to set the threshold for data usage in the instance. When the threshold is reached, you are notified. Enter a value to set the data usage threshold.
4. In the Add recipient section, enter one or more emails where the notification will be sent.
--ge GE
: Specify a minimum matching length (GE, greater than or equal to). Optional. For more information, see [Route filtering rules](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes&interface=uiroute-filtering-rules).

--le LE
: Specify a maximum matching length (LE, less than or equal to). Optional. For more information, see [Route filtering rules](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes&interface=uiroute-filtering-rules).

--help|-h
: Get help on this command. Optional.

--output value
: Specify whether you want the output displayed in JSON format. Currently, json is the only supported format. Optional.





 Examples 



* ibmcloud dl irfu beec5de0-a1c0-4730-8888-2ce4a3020ec8 c3df351b-ff64-4444-ba64-92cb7622dfd6 --action permit
* ibmcloud dl irfu beec5de0-a1c0-4730-8888-2ce4a3020ec8 c3df351b-ff64-4444-ba64-92cb7622dfd6 --le 28









 ibmcloud dl loa 

Download the LOA for the specified gateway in either the current, working directory or in the specified directory.

ibmcloud dl loa GATEWAY_ID [--file OUTPUT_DIRECTORY_PATH] [--help|-h]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

--file OUTPUT_DIRECTORY_PATH
: Specify the output directory path. For example, specify to download the LOA in the /tmp directory. Optional.

--help|-h
: Get help on this command. Optional.





 Examples
For example:

{
"output": {
"generic": [
]
},
"context": {
"smsAction": {
"command": "<command-name>",
"parameters": {
"<first-parameter>": "<parameter-value>"
}
}
}
}







 Sending multimedia content over text 

To allow multimedia content, such as an image, to be sent in a text message, use the smsActSendMedia command.

{
"output": {
"generic": [
]
},
"context": {
"smsAction": {
"command": "smsActSendMedia",
"parameters":{
"mediaURL": [
"https://upload.wikimedia.org/wikipedia/commons/3/39/We_love_kids_but.jpg"
]
}
}
}
}
Show more

You can specify the following parameter value for the vsmsActSendMedia command:



* mediaURL: A JSON array of one or more publicly-accessible media URLs for images or videos.







 Customizing lists 

You can customize how these lists are displayed and handled.



* [Options list](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-sms-actionsdialog-sms-actions-options)
* [Disambiguation](https://cloud.ibm.com/docs/assistant?topic=assistant-dialog-sms-actionsdialog-sms-actions-disambiguation)





 Options list 

The dialog supports an option response type, which shows the customer multiple options to choose from. You can customize how the options that are defined for an option response type are shown to customers and the ways in which a customer can select an option by adding the vgwActSetOptionsConfig action command.

The following example shows how to customize the option response type.

{
"output": {
404 The specified transit gateway could not be found. 







 Example response 

This example illustrates the response that a prefix filter was added successfully:

{
"action": "permit",
"before": "1a15dcab-7e40-45e1-b7c5-bc690eaa9782",
"created_at": "2021-11-15T12:08:05Z",
"ge": 0,
"id": "1a15dcab-7e30-45e1-b7c5-bc690eaa9865",
"le": 32,
"prefix": "192.168.100.0/24",
"updated_at": "2021-11-15T12:08:05Z"
}

For more information (including Java, Node, Python and Go examples), see "Add a prefix filter to a Transit Gateway Connection" in the [Transit Gateway API reference](https://cloud.ibm.com/apidocs/transit-gatewaycreate-transit-gateway-connection-prefix-filter).







 Deleting prefix filters with the API 

To delete prefix filters with the API, follow these steps:



 Request 

To delete prefix filters with the API, adjust the following parameters:



Table 6. Path parameters for deleting prefix filters

 Path parameters Details 

 transit_gateway_id <br>Required <br>string The transit gateway identifier 
 id <br>Required <br>string The connection identifier 
 filter_id <br>Required <br>string The prefix filter identifier 





Table 7. Query parameters for deleting prefix filters

 Query parameters Details 

 version <br>Required <br>string Requests the version of the API as of a date in the format YYYY-MM-DD. Any date up to the current date may be provided. Specify the current date to request the latest version. <br>Possible values: Value must match regular expression ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ 







 Example request
[Image showing alice sending message to protected queue](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_app_ams_st_putpq.png)
4. From bob's command shell, run the sample program to receive the messages.

amqsgetc DEV.QUEUE.1 <your Queue manager name>

4.1 Enter the application API key of bob when prompted for a password(This is your '"apiKey' value in the file "applicationApiKeybob.json)
4.2. You can see that received message message <Hello> confirms that bob is able to read the message data.
![Image showing bob receiving message from protected ueue](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_app_ams_st_getpq.png)







 Message Privacy Check - Data stored as encrypted. 

To demonstrate that the messages are encrypted, we test using an alias queue. Retrieving messages via the alias queue will not trigger the interceptors on the target queue, so the message will be retrieved as it is, without decryption, and so will give an accurate view on whether the message is plain text or encrypted. As part of this demonstration, we run the sender program (amqsputc) using the alice's userid to send a message to protected queue. We then run receiver program (amqsgetc) using the bob's userid to receive the message from an alias queue.



1. Create the following environment variables in alice's command shell.

On Mac:
export MQSAMP_USER_ID=alice
Required if your baseline file is not the default name .secrets.baseline. 
 detect-secrets-exclusion-list String A regex list of files to be excluded in the detect-secrets scan. Defaults to requirements.txt go.modgo.sumpom.xmlbuild.gradlepackage-lock.json. Optional, This file list overrides the general exclusion list only when there is no .secrets.baseline file present. 
 detect-secrets-verbose String Outputs the name of the file that is currently that is being scanned. Defaults to 0. Optional, Debug flag 0 - off, 1 - on.
"accept": "audio/wav"
}

The service first sends a message to confirm the audio format. It then sends multiple messages with the results. The service cannot guarantee the number of audio chunks that it sends to the client or the order in which the text and audio messages are delivered.

Both of the following responses are possible. In each case, the service sends two text messages that identify the locations of the marks in the binary stream. But it sends an arbitrary number of binary messages that contain the audio. The timing information for a mark always arrives before the audio chunk that contains the location of the mark.



* In the first example response, the text messages are interspersed with multiple audio messages:

{
"binary_streams": [
{
"content_type": "audio/wav"
}
]
}
... One or more chunks of binary audio.
All audio precedes the SIMPLE mark....
{
"marks": [

"SIMPLE", 0.784
]
]
}
... One or more chunks of binary audio audio can precede
and follow the SIMPLE mark.
All audio precedes the EXAMPLE mark....
{
"marks": [

"EXAMPLE", 1.003
]
]
}
... One or more chunks of binary audio.
Audio can precede and follow the EXAMPLE mark....
Show more
* In the second example response, the text messages arrive before any of the audio messages:

{
"binary_streams": [
"content_type": "audio/wav"}
]
}
{
"marks": [

"SIMPLE", 0.784
]
]
}
{
"marks": [

"EXAMPLE", 1.003
]
]
}
... One or more chunks of binary audio....
Show more
Do not show the message of the day or update reminders.





 Example 

ibmcloud sat resource get --resource 1234567







 ibmcloud sat resource history get 

Get the history of a Kubernetes resource.

ibmcloud sat resource history --resource RESOURCE [--limit LIMIT] [--output json] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Resource resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--resource RESOURCE
: Required. The ID of the Kubernetes resource. To list Kubernetes resources, run ibmcloud sat resource ls.

--limit LIMIT
: Optional. The maximum number of history entries to return.

--output json
: Optional. Prints the command output in JSON format.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat resource history get --resource 123456 --limit 200







 ibmcloud sat resource ls 

Search for and list Kubernetes resources that are managed by a Satellite configuration.

ibmcloud sat resource ls [--cluster CLUSTER] [--limit NUMBER] [--search STRING] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Resource resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--cluster CLUSTER
: Optional. The name or ID of the registered cluster that the Kubernetes resource runs in. To list registered clusters, run ibmcloud sat cluster ls.

--limit NUMBER
: Optional. Limit the number of Kubernetes resources that are returned.

--search STRING
: Optional.
Zoom

![Admin tab with the Shovel plug-in](https://cloud.ibm.com/docs-content/v1/content/4dfeb7bbbdd817dfbdb17402735fb55d9cfbc7fb/messages-for-rabbitmq/images/plugins-shovel-ui.png)

Figure 1. Admin tab with the Shovel plug-in

If you do not see the Admin tab, you might need to log in to the management UI with the [admin user](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-admin-password).

In the RabbitMQ Management API, the Shovel Management plug-in adds endpoints for listing, creating, and deleting shovels. Usage and examples are in the [GitHub repository's documentation](https://github.com/rabbitmq/rabbitmq-shovel-managementusage).





 Delayed Message plug-in 

The [delayed message plug-in](https://github.com/rabbitmq/rabbitmq-delayed-message-exchange), rabbitmq_delayed_message_exchange is a third-party plug-in that adds delayed messaging and scheduled messaging to RabbitMQ.

To use the plug-in, declare an exchange with the type x-delayed-type. To delay a message, publish it with the x-delay header with the number of milliseconds to delay the message. More detailed usage information is in the [plug-in's documentation](https://github.com/rabbitmq/rabbitmq-delayed-message-exchangeusage).





 STOMP plug-in 

The [RabbitMQ STOMP plug-in](https://www.rabbitmq.com/stomp.html), rabbitmq_stomp, supports sending [STOMP-formatted](http://stomp.github.io/) messages through RabbitMQ.
The value must match regular expression /a-zA-Z 0-9-_/.?:'";,+=@$%^&() ]/.

--ce-ibmenchromebody CE-IBMENCHROMEBODY]ChromeMessageBody]DeviceDataConfiguration]
: Chrome message body to send notification to FCM devices.

--ce-ibmensafaribody CE-IBMENSAFARIBODY]
: Safari message body to send notification to Safari devices.

--ce-ibmenfirefoxbody CE-IBMENFIREFOXBODY]FirefoxMessageBody]DeviceDataConfiguration]
: Firefox message body to send notification to FCM devices.

--ce-ibmenchromeheaders CE-IBMENCHROMEHEADERS]ChromeHeaders]DeviceDataConfiguration]
: The Custom Chrome headers information can be set by using this option.

--ce-ibmenfirefoxheaders CE-IBMENFIREFOXHEADERS]FirefoxHeaders]DeviceDataConfiguration] !
: The Custom Firefox information can be set by using this option.
* Examples:
<-- <ul> -->

* The following example shows the format of data payload for sending notifications.

{
"data": {
"createTimestamp": 1557282940339,
"severity": "LOW",
"shortDescription": "examplestring"
}
}
* The following example shows the format of FCM message body to send notification to FCM devices.

{"message":{
"data":{
If you make a mistake and label the wrong word or a word was labeled incorrectly by the bulk labeling process, you can delete the label.

Hover over the labeled word until the Delete this example option is displayed, and then click it. You can choose to delete only this mention or all of the mentions in the document. Make a choice, and then click Delete.
8. After you label all of the entity examples in the current document, change the document status from In progress to Complete.

Zoom

![Shows the document status menu.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/entity-extractor-mark-complete.png)

Figure 8. Document status menu

Another document from the collection is displayed.
9. Label examples of your entity types in each document in the collection.

At any time during the labeling process, you can click Save entity extractor to save your work.
10. If you don't have enough examples in the current set of documents, you can add more documents.

From the Document list panel, click Add documents. The option is available only when more documents are available in the collection. You can add up to 20 documents. If bulk labeling for all documents is enabled, labels are applied to the newly-added documents automatically.
11. After you label examples in as many documents in the collection as you want, click Save entity extractor, and then open the Train extractor page.







 Labeling examples in bulk 

For most entity examples, enabling the bulk label feature is helpful. You might want to skip it if a term has more than one meaning in different contexts. In that case, evaluate each occurrence individually. Remember, if you enable the bulk label feature, you can check the accuracy of the labels that were added automatically and make corrections when necessary as you review the document.

After you enable the bulk label feature, a notification is displayed that indicates how many occurrences of an entity example were found in the current document.