vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: Specifies an IPv4 subnet CIDR indicating both the address and mask length.

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

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





 Configuring route filters with the API 

To create route filters using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/docs/dl?topic=dl-set-up-environment) with the right variables.
2. Store any additional variables to be used in the API commands, for example:

direct_link_id="11111111-b540-4766-a196-14368f328eb2"
3. Use either the [create an export route filter](https://cloud.ibm.com/apidocs/direct_linkcreate-gateway-export-route-filter) or [create an import route filter](https://cloud.ibm.com/apidocs/direct_linkcreate-gateway-import-route-filter) API. For example, the following Curl example creates an import route filter:



curl -kX POST "https://directlink.cloud.ibm.com/v1/gateways/9a3eac6d-1951-4696-8eca-8b0198f4ddaf/import_route_filters?version=2023-01-02" -H "Authorization: Bearer $token" -d {
"action": "permit",
"ge": 24,
"le": 32,
For more information, see [Prepending an AS path to influence route priority](https://cloud.ibm.com/docs/dl?topic=dl-prepend-as-paths).
* Filter your import routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all import routes are permitted. Next, click Configure filters to start creating import route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration. For more information, see [Filtering routes](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes).
* Filter your export routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all export routes are permitted. Next, click Configure filters to start creating export route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration. For more information, see [Filtering routes](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes).



10. In the Connections section, select the type of network connection that you want to bind to the Direct Link gateway. You can select a connection type when you create a direct link, or after your direct link is provisioned.

Select from the following connection types:



* Select Direct resources (default) to create a direct, private connection between your on-premises network and IBM Cloud deployment. Optionally, choose a connection and enter a connection name. To add multiple network connections to the Direct Link gateway, click Add connection +. You can create one of the following connections:



* Classic infrastructure networks allow you to connect to IBM Cloud classic resources. Only one classic infrastructure connection is allowed per Direct Link gateway.
* VPC networks allow you to connect to your account’s VPC resources.



You cannot request a connection to a network in another account when you create a gateway. However, you can request a connection to a network in another account after a gateway is provisioned.
You can add prefix filters when you add a new connection. You can also add a filter to an existing connection, or delete them.



 Adding prefix filters to a new connection 

To add a prefix filter to a new connection in the UI, follow these steps:



1. From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2. Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) from the upper left, then click Interconnectivity.
3. Click Transit Gateway from the left navigation pane to show the Transit Gateway page.
4. From the Transit Gateway page, click the name of the the gateway where you want to add prefix filters.
5. From the gateway's details page, click Add connection.
6. Enter the following information:

Review requirements and configuration considerations in [Planning for Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-helpful-tips).



* Choose a network connection. You can select from the following connection types:



* Classic infrastructure networks allow you to connect to IBM Cloud classic resources. Only one classic infrastructure connection is allowed per account.
* VPC networks can contain compute resources, allowing you to connect to your account's VPC resources, or, with approval, another account's VPC resources.
* Direct Link creates a network connection to and from Direct Link 2.0 gateways so that there is a secure connection to on-premises networks and other resources connected to the transit gateway.

If you select Direct Link, you must also log in to the [Direct Link console](https://cloud.ibm.com/interconnectivity/direct-link) (using the same IBM Cloud account) and specify Transit Gateway as the type of network connection for your direct link. You can specify the connection type when you create a direct link, or after your direct link is provisioned.
[VMware compatibility guide](https://www.vmware.com/resources/compatibility/search.php?deviceCategory=vasa) 
 Registration or unregistration of third-party IO filter storage providers fails on a host Not configured in vCenter Server instances as they do not support VASA storage. [VMware compatibility guide](https://www.vmware.com/resources/compatibility/search.php?deviceCategory=vasa) 
 Service Control Agent Health Alarm Configure to send email one time when component ID equal to sca and New status equal to red. [How to stop, start, or restart vCenter Server 6.x services (2109881)](https://kb.vmware.com/s/article/2109881) 
 Identity Health Alarm Configure to send email one time when component ID equal to identity and New status equal to red. [How to stop, start, or restart vCenter Server 6.x services (2109881)](https://kb.vmware.com/s/article/2109881) 
 vSphere Web Client Health Alarm Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [Enabling debug logging on the VMware vSphere 5.x/6.x Web Client service (2011485)](https://kb.vmware.com/s/article/2011485) 
 ESX Agent Manager Health Alarm Configure to send email one time when component ID equal to eam and New status equal to red. [How to stop, start, or restart vCenter Server 6.x services (2109881)](https://kb.vmware.com/s/article/2109881) 
 Message Bus Config Health Alarm Not considered essential for notification. Alarm that is reviewed as part of proactive daily checks. [How to stop, start, or restart vCenter Server 6.x services (2109881)](https://kb.vmware.com/s/article/2109881)
: To forward logs from apps, you can specify the name of the container that contains your app. To specify more than one container, use multiple options, such as -C /var/log/myApp1/&ast; -C /var/log/myApp2/&ast;. If no containers are specified, logs are forwarded from all the containers that contain the paths that you provided. This option is only valid for log source application.

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

--skipValidation
: Optional: Skip validation of the org and space names when they are specified. Skipping validation decreases processing time, but an invalid logging configuration does not correctly forward logs.

--force-update
: Force your Fluentd pods to update to the latest version. Fluentd must be at the latest version to change your logging configurations.

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

Example for log type ibm:

ibmcloud ks logging config update --cluster my_cluster --id f4bc77c0-ee7d-422d-aabf-a4e6b977264e --type ibm

Example for log type syslog:

ibmcloud ks logging config update --cluster my_cluster --id f4bc77c0-ee7d-422d-aabf-a4e6b977264e --hostname localhost --port 5514 --type syslog





 ibmcloud ks logging filter create 

Virtual Private Cloud

Classic infrastructure

Filter out logs that are forwarded by your logging configuration.

ibmcloud ks logging filter create --cluster CLUSTER --type LOG_TYPE [--logging-config CONFIG] [--namespace KUBERNETES_NAMESPACE] [--container CONTAINER_NAME] [--level LOGGING_LEVEL] [--message MESSAGE] [--regex-message MESSAGE] [--force-update] [--output json] [-q]

Minimum required permissions
Then, restart syslog. Run systemctl restart rsyslog.







 Step 1: Step 2. Configure vCenter Server to send logs to a remote rsyslog server 

By default, sending logs to a remote rsyslog server is not enabled for the vCenter Server.



 Enable vCenter Server to send logs 

Complete the following steps to enable sending logs to a remote rsyslog server from the vCenter Server:



1. Launch the vSphere Client.
2. Select the vCenter Server instance. Then, select Configure > Settings > Advanced System Settings.

Zoom

![Configure vCenter](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/vmware-vcenter-settings.png)

Figure 3. Edit Advanced vCenter Server Sttings
3. Click EDIT SETTINGS and search for entries that have the prefix vpxd.event.
4. Enable the setting vpxd.event.syslog.enabled.
5. Click SAVE.







 Filter the logs that vCenter Server sends 

In vCenter, you can change the logging policy for ESXi hosts to reduce the number of logs collected per component. All the logs that are processed by the ESXi host vmsyslogd service are impacted.

You can create log filters:



* To reduce the number of repetitive entries in the ESXi logs by stopping logging after a maximum number of log entries is reached.
* To remove specific log events.



Reducing logs helps reduce logging costs. However, you should keep all the logs that you need for operations, troubleshooting and compliance.

Complete the following steps to configure filtering in an ESXi host:



1. Launch the vSphere Client.
2. Select the ESXi host that you want to modify. Then, select Configure > System > Advanced System Settings.
3.
-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"]}}}}'

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





 Authorizing access to private catalogs by using the API 

To authorize users to work with the products in your private catalogs, assign them the [viewer role on the catalog management service](https://cloud.ibm.com/docs/account?topic=account-account-servicesapi-acct-mgmt).





 Deleting a private catalog by using the API 

If you delete a private catalog, all of the products within the catalog are deleted as well. Use the following command to delete a private catalog:

DELETE /catalogs/{catalog_identifier}

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

You can [restore a private catalog](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation&interface=apirestore-resource-api) within 7 days after you delete it.





 Creating a private catalog by using Terraform 

Use the following steps to create a private catalog:



1. Create an argument in your main.tf file.
enable_dtmf_barge_in dtmf, command_info.type : enable_barge_in 
 disable_dtmf_barge_in dtmf, command_info.type : disable_barge_in 
 hangup end_session 







 assistant_interaction_summaries.turns[].response.streaming_statistics 

The assistant_interaction_summaries.turns[].response.streaming_statistics object contains the following properties:



Properties of the assistant_interaction_summaries.turns[].response.streaming_statistics object

 Property Type Description 

 transaction_id String A unique identifier of the transaction. 
 start_timestamp String The time when the transaction started, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 stop_timestamp String The time when the transaction ended, in ISO format (yyyy-MM-ddTHH:mm:ss.SSSZ). 
 response_milliseconds Number The time (in milliseconds) between when a text utterance is sent to the assistant and when the phone integration receives the first packet of synthesized audio. 













 warnings_and_errors 

The warnings_and_errors object contains warnings and errors that were logged during the call, listed in order of occurrence. Warnings for the following conditions are included:



* Messages when utterances are filtered out by the confidence score threshold.
* Text to Speech underflows, which is when Text to Speech synthesis can't keep up with the phone integration streaming rate and audio might skip.
* RTP network warnings, such as high packet loss or high average jitter, if RTCP is enabled.



The following example shows the structure of the warnings_and_errors object:

"warnings_and_errors": [
{
"message": "CWSMR0032W: A Watson Speech to Text final utterance has a confidence score of 0.1, which does not meet the confidence score threshold of 0.2. The utterance will be ignored.",
"id": "CWSMR0032W"
},
{
Go to Manage > Catalogs, Private catalogs in the IBM Cloud console.
2. Select a catalog from the list to navigate to its details page.

The Products in the IBM Cloud catalog table that's displayed on the page shows the list of products that are available at the account level. The availability is based on the filters the account owner or administrator set. Account-level filters apply to all the private catalogs in the account.
3. Click Manage filters.
4. Select to include or exclude all products in the public catalog.
5. Set one or more [filters](https://cloud.ibm.com/docs/account?topic=account-filter-accountcatalog-filters-customize) to customize what products are available by category.
6. (Optional) Add exceptions to the filter rules that you set in the previous step.
7. Click Update.
8. Go to the Settings page and turn off the visibility of the public catalog.
9. To give users access to work with the products in the private catalog, assign them the [viewer role on the catalog management service](https://cloud.ibm.com/docs/account?topic=account-account-servicescatalog-management-account-management).



For more detailed examples of how you can leverage filtering at the private catalog level, see [Customizing your private catalogs](https://cloud.ibm.com/docs/account?topic=account-restrict-by-user).





 Updating the visibility of the IBM Cloud catalog by using the CLI 

Users in your account have access to all products in the IBM Cloud public catalog by default. 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.

ibmcloud catalog filter hide-ibm-public-catalog





 Managing access to products for all users by using the CLI 

You can use filters to manage which products in the public catalog are available to all users in your account.
* Direct Link creates a network connection to and from Direct Link 2.0 gateways so that there is a secure connection to on-premises networks and other resources connected to the transit gateway.

If you select Direct Link, you must also log in to the [Direct Link console](https://cloud.ibm.com/interconnectivity/direct-link) (using the same IBM Cloud account) and specify Transit Gateway as the type of network connection for your direct link. You can specify the connection type when you create a direct link, or after your direct link is provisioned. For instructions, see [Updating the network connection type](https://cloud.ibm.com/docs/dl?topic=dl-virtual-connection-types).



* For Connection reach, select one of the following options:



* Add new connection in this account - Enter an optional connection name.
* Request connection to a network in another account - Enter the IBM Cloud ID of the account that manages the network that you want to connect to, and a connection name. All resources connected to that transit gateway will be accessible from the other network.



* Complete all other required information for your connection.



7. Optionally, you can create prefix filters to permit or deny specific routes on specific connections.

To begin, expand the drop-down arrow in the upper right of the Prefix filtering section. Then, complete the following information:



* Adjust the Default filter as needed. Your choices are as follows:



* Permit prefixes (default) accepts all prefixes after entries in the prefix filter list are processed.
* Deny prefixes denies all prefixes after entries in the prefix filter list are processed.



Regardless of the default setting, you can still permit or deny network traffic by creating prefix filters.
* To create a prefix filter, select Create prefix filter, then complete the following information:



* Select an action type: Permit or Deny.
* Enter the network prefix along with its subnet mask (for example, 10.0.0.0/16).
* Optionally, enter values for whether the network should be greater than or equal to the subnet mask you chose.
* Click Save to add the prefix filter.
ibmcloud dl export-route-filter-delete 

Delete an export route filter.

ibmcloud dl export-route-filter-delete|erfd 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 export route filter that you want to delete.

--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 erfd beec5de0-a1c0-4730-8888-2ce4a3020ec8 c3df351b-ff64-4444-ba64-92cb7622dfd6









 ibmcloud dl export-route-filter-replace 

Replace all export route filters.

ibmcloud dl export-route-filter-replace|erfr GATEWAY_ID --file JSON_FILE --etag ETAG [-–help|-h] [--output format]



 Command options 

GATEWAY_ID
: 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 erfr 58e4f46f-0dab-4025-9999-3df974db0618 --etag 'W/"182-9c1ba4f4ab697f4080f662c18e664d5763ae4b8dcb0542b4b473d661"' --file /export.txt
{
"name": "Retrieve list of failed multipart uploads (filter by name)",
"event":
{
"listen": "test",
"script": {
"id": "835bcaf6-6e7d-4fa9-883e-1a5c5538ac7e",
"type": "text/javascript",
"exec":
"pm.test("Request was successful", function() {",
" pm.response.to.be.success; ",
"});",
"",
"pm.test("Response contains expected content", function() {",
" pm.expect(pm.response.text()).to.include("ListMultipartUploadsResult");",
"});"
]
}
}
],
"request": {
"auth": {
"type": "bearer",
"bearer":
{
"key": "token",
"value": "{{iamtoken}}",
"type": "string"
}
]
},
"method": "GET",
"header": ],
"body": {
"mode": "raw",
"raw": ""
},
"url": {
"raw": "https://{{endpoint-region}}cloud-object-storage.appdomain.cloud/{{bucket}}?uploads=&prefix=my",
"protocol": "https",
"host":
"{{endpoint-region}}",
"objectstorage",
"softlayer",
"net"
],
"path":
"{{bucket}}"
],
"query":
{
"key": "uploads",
Go to Manage > Catalogs, Private catalogs in the IBM Cloud console.
2. Select a catalog from the list to navigate to its details page.

The Products in the IBM Cloud catalog table that's displayed on the page shows the list of products that are available at the account level. The availability is based on the filters the account owner or administrator set. Account-level filters apply to all the private catalogs in the account.
3. Click Manage filters.
4. Select to include or exclude all products in the public catalog.
5. Set one or more [filters](https://cloud.ibm.com/docs/account?topic=account-filter-account&interface=uicatalog-filters-customize) to customize what products are available by category.
6. (Optional) Add exceptions to the filter rules that you set in the previous step.
7. Click Update.
8. Go to the Settings page and turn off the visibility of the public catalog.
9. To give users access to work with the products in the private catalog, assign them the [viewer role on the catalog management service](https://cloud.ibm.com/docs/account?topic=account-account-servicescatalog-management-account-management).



For more detailed examples of how you can leverage filtering at the private catalog level, see [Customizing your private catalogs](https://cloud.ibm.com/docs/account?topic=account-restrict-by-user).





 Updating the visibility of the IBM Cloud catalog by using the CLI 

Users in your account have access to all products in the IBM Cloud public catalog by default. 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.

ibmcloud catalog filter hide-ibm-public-catalog





 Managing access to products for all users by using the CLI 

You can use filters to manage which products in the public catalog are available to all users in your account.
[Filter icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/filter.png) to filter the graph by a specific field's data. For example, host:myhost.
15. Click the Pencil icon ![Pencil icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/pencil.png) and enter a name for your dashboard. Specify a Category if desired and click Save.



If you don't specify a Category your dashboard will be listed under UNCATEGORIZED. If you are editing an existing dashboard, changes will be saved when exiting the dashboard without having to click Save.





 Step 9: Create a widget in a screen 

Using the screen option you can create a screen of widgets that you can use to monitor your app using metrics (counters), operational KPIs (gauges), tables, and graphs that can be used to analyze patterns and trends.



1. [Make sure you are logged in to the IBM Cloud and have accessed the IBM Log Analysis web UI](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-tutorial-use-logdnaLA-launch-ui).
2. Click the Screens icon ![Screens icon](https://cloud.ibm.com/docs-content/v1/content/f61dbc5d84bf0c89e477a05cab04c72f429e1b7a/log-analysis/images/screens.png).
3. Click NEW SCREEN.
4. To save the screen, click Save Screen. Enter the following and then click Save.

Name: The name you want to give to your screen.