vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud dl import-route-filter-create|irfc GATEWAY_ID --action ACTION --prefix PREFIX [--before BEFORE] [--ge GE] [--le LE] [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

--action ACTION
: Specify the import route filter action. One of permit, deny.

--prefix PREFIX
: Specify an IPv4 subnet CIDR indicating both the address and mask length.

--before BEFORE
: To prioritize this filter in the import route filter list, specify the ID of the route filter that comes before this filter. Optional.

--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 irfc dc206f57-5693-442f-8888-6d43b6c82d73 --action permit --prefix 10.10.0.0/24
* ibmcloud dl irfc dc206f57-5693-442f-8888-6d43b6c82d73 --action deny --prefix 10.10.0.0/24 -le 29









 ibmcloud dl import-route-filter-delete 

Import an export route filter.
Add the use_container_filter entry and container_filter section or update the the existing entries.

For example, see the following extract of a config map:

 Enable the feature
use_container_filter: true

 Include or exclude conditions
container_filter:
- include:
container.image: appdomain/my-app-image
- include:
container.name: my-java-app
- exclude:
kubernetes.namespace.name: kube-system
4. Save the changes.



Changes are applied automatically.





 Blocking ports 

To block network traffic and metrics from network ports, you must customize the blacklisted_ports section in the sysdig-agent-configmap.yaml file. You must list the ports from which you want to filter out any data.

Port 53 (DNS) is always in the blocklist and does not need to be specified in the blacklisted_ports.

Complete the following steps:



1. Set up the cluster environment. Run the following commands:

First, get the command to set the environment variable and download the Kubernetes configuration files.

ibmcloud ks cluster config --cluster <cluster_name_or_ID>
2. Edit the sysdig-agent-configmap.yaml file.

Run the following command:

kubectl edit configmap sysdig-agent -n ibm-observe
3. Make changes. Add the metrics_filter section or update the section.

For example, the following sample shows how to set the blacklisted_ports section of a monitoring agent to exclude data coming from ports 6666 and 6379:

blacklisted_ports:
- 6666
- 6379
4. Save the changes.



Changes are applied automatically.





 Changing the log configurations 

To configure the log configurations, you must customize the log section in the sysdig-agent-configmap.yaml file.

The monitoring agent generates log entries in /opt/draios/logs/draios.log.
IBM Cloud Email service 

Event Notifications provides a built-in SMTP server for sending transactional and informational event notification emails to recipients who need to be aware of events that happen within your IBM Cloud account.

The emails originate from no-reply@cloud.ibm.com or event-notifications@cloud.ibm.com, but you can add your own reply-to address. Except for test emails, the content cannot be modified within Event Notifications.

Zoom

![Email state-diagram](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-email-state-diagram.png)

Figure 1. Email state diagram



 Adding an email service destination 

IBM Cloud email service is a destination that is provided as ready for immediate use. When a new instance is created, you see an entry IBM Cloud Email service in the destination tab. The email destination is pre-configured, and is ready to use.





 Using an IBM Cloud email service destination 

To use the email service destination, add it to a subscription along with the email addresses of interest. Within a single subscription, you can add up to 100 email recipients. The subscription also needs a topic to filter events of interest from your sources. When an event lands in the topic, Event Notifications immediately routes the event notification to your email recipients.

If you add an individual to the recipient list who does not want to receive email notifications, the recipient can opt out by clicking a link in the footer of the email. You can track recipients who opt into the Event Notifications dashboard.

By adding email addresses, you represent on behalf of yourself and your company that you inform the individuals, to whom the added emails pertain, of their addition to this recipient list and purpose thereof, and have the required consents to do so.

After a subscription is created, the list of users in the Invited tab automatically receives initial message with information that they are invited to subscribe to the list, which is the "Opt-in" message.
[Type ^D at a new line to end input]
family inet {
filter {
input PROTECT-IN;
}
}
load complete

[edit interfaces lo0 unit 0]



Alternatively, you can also:



* Replace the configuration instead of merging it, by deleting the configuration first with the command delete under this configuration tree level and then performing a load merge terminal relative to copy and paste your previous configuration.
* Edit the configuration in set mode, by running load set terminal instead of load merge terminal relative. Then copy and paste the content you saved in set mode.

Ensure that you always run load set terminal at the top.
: Specify the ID of the gateway.

--file JSON_FILE
: Specify the JSON file for input data.

--etag ETAG
: Specify the eTag.

--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.





 Example 

ibmcloud dl irfr 58e4f46f-0dab-4025-9999-3df974db0618 --etag 'W/"182-9c1ba4f4ab697f4080f662c18e664d5763ae4b8dcb0542b4b473d661"' --file /import.txt







 ibmcloud dl import-route-filter-update 

Update an import route filter.

ibmcloud dl import-route-filter-update|irfu GATEWAY_ID [--action ACTION] [--prefix PREFIX] [--before BEFORE] [--ge GE] [--le LE] [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

--action ACTION
: Specify the import route filter action. One of permit, deny. Optional.

--prefix PREFIX
: Specify an IPv4 subnet CIDR indicating both the address and mask length. Optional.

--before BEFORE
: To prioritize this filter in the import route filter list, specify the ID of the route filter that comes before this filter. Optional.

--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.
Filtering functions 

Each of these functions returns the subsequence of a time series that satisfies the filter criteria.

TS_SLICE(TimeSeries, Long, Long)
: Output: TimeSeries
: Returns the subsequence of the specified time series that lies between the specified start time (second parameter) and end time (third parameter).

TS_REMOVE_CONSECUTIVE_DUPLICATES(TimeSeries)
: Output: TimeSeries
: Removes consecutive duplicate values from the specified time series.

TS_COMBINE_DUPLICATE_TIMETICKS(TimeSeries, CombinerType)
: Output: TimeSeries
: Combines observations with duplicate timeticks based on the specified [combiner](https://cloud.ibm.com/docs/services/sql-query?topic=sql-query-artifactcombiner_creation).

TS_INDEX (ArrayTimeSeries, Integer)
: Output: TimeSeries
: Returns a time series whose values correspond to the values of the input array time series at the specified index (second parameter).

TS_FILTER (time_series, Boolean expression)
: Output: TimeSeries
: Filter each value of the time series given a Boolean expression.





 Cleaning functions 

Each of these functions removes null values from time series.

TS_FILLNA

[1]

(InterpolatorType)
: Output: The output is of the same type as the input.
: Replace each null value with a new value as determined by the specified [interpolator](https://cloud.ibm.com/docs/services/sql-query?topic=sql-query-artifactinterpolator_creation).

TS_DROPNA

[2]

: Output: The output is of the same type as the input.
: Drop all observations that contain at least one null value.





 Segmentation functions 

Each of these functions creates, as output, a segmented version of a time series. The lengths of the segments are determined by [anchor points](https://cloud.ibm.com/docs/services/sql-query?topic=sql-query-artifactanchor_creation).

TS_SEGMENT

[3]
You can make products available only to the users you choose by turning off visibility to the IBM Cloud catalog and adding the products to your private catalogs. Use the following command to turn off visibility of the public catalog to all users in your account.

curl -X "PUT" "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogaccount"
-H "accept: /"
-H "Authorization: {iam-bearer-token}"
-d '{"id":"string","hide_IBM_cloud_catalog":true,"account_filters":{"include_all":true,"category_filters":{"additionalProp1":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp2":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp3":{"include":true,"filter":{"filter_terms":["string"]}}},"id_filters":{"include":{"filter_terms":["string"]},"exclude":{"filter_terms":["string"]}}}}'

Make sure the hide_IBM_cloud_catalog field has a Boolean value of true to hide the public catalog in this account. Alternatively, you can give the include_all field a Boolean value of false for each account_filters object to exclude all of the public catalog.

See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=curlupdate-catalog-account) for more information.





 Managing access to products for all users by using the API 

You can use filters to manage which products in the public catalog are available to all users in your account. For example, you might want to restrict access to third-party products. Or, you might want users to work with a specific software type.
const service = CloudantV1.newInstance({});

service.postChanges({
db: 'orders',
filter: '_doc_ids',
docIds: ['ExampleID']
}).then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.post_changes(
db='orders',
filter='_doc_ids',
doc_ids=['ExampleID']
).get_result()

print(response)

postChangesOptions := service.NewPostChangesOptions(
"$DATABASE",
)
postChangesOptions.SetFilter("_doc_ids")
postChangesOptions.SetDocIds([]string{"ExampleID"})

changesResult, response, err := service.PostChanges(postChangesOptions)
if err != nil {
panic(err)
}

b, _ := json.MarshalIndent(changesResult, "", " ")
fmt.Println(string(b))

The previous Go example requires the following import block:

import (
"encoding/json"
"fmt"
"github.com/IBM/cloudant-go-sdk/cloudantv1"
)

See the following example JSON document that lists document IDs to match during filtering:

{
"doc_ids": [
"ExampleID"
]
}

See the following example response (abbreviated) after you filter by _docs_ids:

{
"last_seq":"5-g1A...o5i",
"pending":0,
"results":[
{
"changes":
{
So continuing the preceding examples, if filter B has an empty before field, then it is applied last, but if filter D is created with an empty before field, then B's before field is modified to point to D, so B is applied before D. <br> Example: 1a15dcab-7e40-45e1-b7c5-bc690eaa9782<br><br><br> 
 ge <br>integer IP prefix greater than or equal to this number is processed. 
 le <br>integer IP prefix less than or equal to this number is processed. 







 Example request 

This example illustrates adding a prefix filter to a connection:

curl -X POST --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/json" --data '{ "action": "permit", "prefix": "192.168.100.0/24" }' "{base_url}/transit_gateways/{transit_gateway_id}/connections/{id}/prefix_filters?version={version}"

POST /transit_gateways/{transit_gateway_id}/connections/{id}/prefix_filters

curl -X POST "https://transit.cloud.ibm.com/v1/transit_gateways/9f559c43-63f4-4da5-b306-b525a8ddb275/connections/6c1bdc19-4adb-4550-8cdc-ef3b74b739f8/prefix_filters?version=2020-03-31" -H "Authorization: Bearer $iam_token" -H "Content-Type: application/json" -d '{"action": "deny", "prefix": "10-10.0.10/30"}'





 Response 

The following response details show once you initiate the request:



Table 4. Response details for adding prefix filters

 Response body Details
ibmcloud dl import-route-filter 

View details of an import route filter by ID.

ibmcloud dl import-route-filter|irf GATEWAY_ID FILTER_ID [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

FILTER_ID
: Specify the ID of the import route filter that you want to list.

--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.





 Example 

ibmcloud dl irf beec5de0-a1c0-4730-8888-2ce4a3020ec8 c3df351b-ff64-4444-ba64-92cb7622dfd6







 ibmcloud dl import-route-filters 

List all import route filters.

ibmcloud dl import-route-filters|irfs GATEWAY_ID [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

--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.





 Example 

ibmcloud dl irfs beec5de0-a1c0-4730-8888-2ce4a3020ec8







 ibmcloud dl import-route-filter-create 

Create an import route filter.

ibmcloud dl import-route-filter-create|irfc GATEWAY_ID --action ACTION --prefix PREFIX [--before BEFORE] [--ge GE] [--le LE] [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

--action ACTION
: Specify the import route filter action. One of permit, deny.

--prefix PREFIX
Response contains expected header 
 Retrieve list of files from bucket (filter by prefix) Change the querystring value to prefix=<some text>. In the body of the response you see the files with names that start with the prefix specified. Request was successful. Response contains expected header 
 Retrieve text file In the Body of the response you see the text you entered in the previous request Request was successful. Response contains expected body content. Response contains expected header 
 Retrieve binary file In the Body of the response you see the image you chose in the previous request. Request was successful. Response contains expected header 
 Retrieve list of failed multipart uploads In the Body of the response you see any failed multipart uploads for the bucket. Request was successful. Response contains expected content 
 Retrieve list of failed multipart uploads (filter by name) Change the querystring value to prefix=<some text>. In the body of the response you see any failed multipart uploads for the bucket with names that start with the prefix specified. Request was successful. Response contains expected content 
 Set CORS enabled bucket Status Code 200 OK Request was successful 
 Retrieve bucket CORS config In the body of the response you see the CORS configuration set for the bucket Request was successful. Response contains expected content 
 Delete bucket CORS config Status Code 200 OK Request was successful 
 Delete text file Status Code 200 OK Request was successful 
 Delete binary file Status Code 200 OK Request was successful 
 Delete bucket Status Code 200 OK Request was successful 
 Create new bucket (different storage class) Status Code 200 OK Request was successful 
 Delete bucket (different storage class) Status Code 200 OK Request was successful 
 Create new bucket (key protect) Status Code 200 OK Request was successful 
 Delete bucket (key protect) Status Code 200 OK Request was successful 









 Using the Postman Collection Runner 

The Postman Collection Runner provides a user interface for testing a collection and allows you to run all requests in a Collection at once.



1. Click the Runner button in the upper right corner on the main Postman window.
2.
Optional.





 Example 

ibmcloud dl erfr 58e4f46f-0dab-4025-9999-3df974db0618 --etag 'W/"182-9c1ba4f4ab697f4080f662c18e664d5763ae4b8dcb0542b4b473d661"' --file /export.txt







 ibmcloud dl export-route-filter-update 

Update an export route filter.

ibmcloud dl export-route-filter-update|erfu GATEWAY_ID [--action ACTION] [--prefix PREFIX] [--before BEFORE] [--ge GE] [--le LE] [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

--action ACTION
: Specify the export route filter action. One of permit, deny. Optional.

--prefix PREFIX
: Specify an IPv4 subnet CIDR indicating both the address and mask length. Optional.

--before BEFORE
: To prioritize this filter in the export route filter list, specify the ID of the route filter that comes before this filter. Optional.

--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.
: Specify a HCL Notes formula to use to filter the data that you want to crawl. For example, SELECT @IsAvailable(Year) & Year > 2003.

For more information, see [Formula language](https://help.hcltechsw.com/dom_designer/10.0.1/basic/H_NOTES_FORMULA_LANGUAGE.html) in the HCL Notes documentation.
11. Specify the date that you want to use when you filter the documents. The date is stored in a field that is named _ _$Date$_ _ in HCL Notes documents. By default, the field stores the last modified date of the document. You can choose a different date to store in the field instead.

Document modification date
: Uses the date that the document was last modified. This option is selected by default.

Document crawl date
: Uses the last crawled date.

Document creation date
: Uses the creation date of the document.
12. If you want the crawler to extract text from images in documents, expand More processing settings, and set Apply optical character recognition (OCR) to On.

When OCR is enabled and your documents contain images, processing takes longer. For more information, see [Optical character recognition](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionsocr).
13. Click Finish.



The collection is created quickly. It takes more time for the data to be processed as it is added to the collection.

If you want to check the progress, go to the Activity page. From the navigation pane, click Manage collections, and then click to open the collection.
The filter was applied to those objects and found 645 enriched_text.entities of type Organization.





 Terminal operations 

For most aggregation types, when you construct a query with multiple aggregation operations, the first operation is applied to the documents. Then, the output of that operation is used as the input for the next operation. However, a subset of the aggregation types are terminal operations. The output of a terminal operation is not used as input for the next aggregation. Instead, the output is returned in a discrete group.

For an example of a request that combines aggregation types and includes an aggregation that performs a terminal operation, see the second [example](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsaverage-example) for the average aggregation type.







 Aggregation types 

The following types of aggregations are supported:



* [average](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsaverage)
* [filter](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsfilter)
* [group_by](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsgroup_by)
* [histogram](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationshistogram)
* [max](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsmax)
* [min](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsmin)
* [nested](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationsnested)
* [pair](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-query-aggregationspair)
You can access the SUMA configuration by running the [suma command](https://www.ibm.com/support/knowledgecenter/ssw_aix_72/s_commands/suma.html) or by using the SMIT suma fast path. When you create a SUMA policy, you must specify one of the following request types that specifies the type of download:



* PTF: Specifies a request to download a program temporary fix (PTF), such as U813941. Only certain PTFs can be downloaded as an individual file set. This limitation applies to PTFs that contain either the bos.rte.install or bos.alt_disk_install.rte file sets as well as those that are released in between Service Packs (SP). Otherwise, you must download the technology level (TL) or SP.
* TL: Specifies a request to download a specific TL (such as 7200-02).
* SP: Specifies a request to download a specific SP (such as 7200-02-00).
* Latest: Specifies a request to download the latest fixes. This value returns the latest SP or TL as specified in the FilterML attribute.







 Configuring SUMA to use the proxy settings 

Before you run the suma command to download any updates, ensure that the AIX LPAR is authenticated to access the internet. To verify that the LPAR is connected to the internet, enter the following command:

suma -x -a Action=Preview -a RqType=LatestCopy

The suma command allows you to preview only the download operation. When you run this command, files are not downloaded. If the LPAR is not authenticated to access the internet, the command returns an error message. For information on troubleshooting SUMA error messages, see [Troubleshooting SUMA error messages](https://www.ibm.com/support/knowledgecenter/ssw_aix_72/install/serv_update_mgt.htmlserv_update_mgt__section_troubleshoot_suma).

0500-013 Failed to retrieve list from fix server.