vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Viewing all subnets 

The Subnets page lists each subnet that is associated with the account, along with specific information about the subnet, including its network, type, VLAN, location, target, and total number of IP addresses. Follow these steps to view the Subnets page.



1.  From your browser, open the [IBM Cloud console](https://cloud.ibm.com/) and log in to your account.
2.  From the dashboard, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) and select Classic Infrastructure.
3.  Select Network > IP Management > Subnets.





  Filtering the list of subnets 

The list of subnets can be filtered to narrow the subnets displayed at any time. Follow these steps to filter the information shown in the Subnets page.



1.  Expand the Filter subnets section to display the filter options.
2.  Specify values for one or more items in the menu list. Filter options include:



*  Subnet
*  Network
*  Type
*  VLAN
*  Location
*  Target
*  Note



3.  Click Filter to apply the selected filters to the display.



After filtering, all subnets that correspond with the parameters set by the filter are displayed on the Subnets page. To clear all parameters set by the filter, click Clear.

The search bar acts on the filtered results. If you have no filters selected, it searches all subnets.





  Other actions available 

On the Subnets page, each subnet that is associated with the account is displayed within the list of subnets. From this page, you can view a subnet or VLAN's details, edit notes for a subnet, or order more IP addresses.

Click the download icon ![Download icon](https://cloud.ibm.com/docs-content/v1/content/88335aaac95959c46c027441a146a8971be515cd/icons/download.svg) to download a comma-separated value file of your subnets.

If you have filters applied in the Filter subnets section, the CSV file contains only those filtered subnets. If no filters are applied, the CSV file contains all of your subnets. Any search bar filters in use have no effect on the contents of the CSV file.
{"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"}





 Modifying views 

When you modify a view, consider the following information:



* You must specify the name and the view ID of the view.
* If you are viewing a view in the logging web UI, the view is not refreshed automatically after you run an API request to modify the view. To refresh the view in the UI, you must navigate to the Everything view and back to the view.



An API request to modify a view replaces the existing view definition and associated alerts with your request body data. Any properties that are not specified in your PUT request will be removed.

If the viewid that you are trying to modify does not exist, a response similar to the following will be returned:

{"error":"Nothing to configure","code":"BadRequest","status":"error"}





 Deleting views 

When you delete a view, consider the following information:



* You must specify the ID of the view that you plan to delete.
* You delete the view and all the alerts that are configured for the view.
: Optional: Do not show the message of the day or update reminders.



 Example ingress alb get command 

ibmcloud oc ingress alb get --alb public-cr18a61a63a6a94b658596aa93a087aaa9-alb1 --cluster mycluster







 ibmcloud oc ingress alb health-checker disable 

Virtual Private Cloud

Classic infrastructure

Disable the health checker for an Ingress ALB in a cluster.

ibmcloud oc ingress alb health-checker disable --cluster CLUSTER [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: The name or ID of the cluster.

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



 Example ingress alb health-checker disable command 

ibmcloud oc ingress alb health-checker disable --cluster mycluster







 ibmcloud oc ingress alb health-checker enable 

Virtual Private Cloud

Classic infrastructure

Enable the health checker for an Ingress ALB in a cluster.

ibmcloud oc ingress alb health-checker enable --cluster CLUSTER [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: The name or ID of the cluster.

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



 Example ingress alb health-checker enable command 

ibmcloud oc ingress alb health-checker enable --cluster mycluster







 ibmcloud oc ingress alb health-checker get 

Virtual Private Cloud

Classic infrastructure

View the details of the health checker for an Ingress ALB in a cluster.

ibmcloud oc ingress alb health-checker get --cluster CLUSTER [--output OUTPUT] [-q]
Error messages 

These error messages are created by Key Protect and shown in the user interface (UI).

Most error messages have one or more examples, usually curl, that show the request and response.

This is not a complete list of error messages. Some messages are created by other systems, such as identity and access management (IAM), where the error message is passed from another system, such as IAM, to Key Protect to the user.



 Table of contents 

The table of contents is sorted by the error message.



* The first list [sorts the error messages by HTTP status code](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-sorted-by-http-status-code)
* Another list [sorts the error messages by reason code](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-sorted-by-reason-code)



Some error messages occur more than once, in those cases the HTTP status code is included at the end of the error message.



1. Collection total does not match number... [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-collection-total-mismatch-err)
2. Data in body does not match data required... [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-body-query-param-mismatch-err)
3. Extracting the subject from the bearer... [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-bearer-sub-extraction-err)
4. Invalid body data was passed... [details](https://cloud.ibm.com/docs/key-protect?topic=key-protect-error-messageserror-messages-bad-body-err)
5.
* Left to Right to keep the longest result, with the greatest number of terms from left - to right.





As an example, you are designing an extractor for documents that include references to military personnel. After you create and run a dictionary containing a list of military ranks, such as Chief Warrant Officer, Warrant Officer, and Officer, you see the following results for Chief Warrant Officer John Doe:



* Chief Warrant Officer John Doe
* Warrant Officer John Doe
* Officer John Doe



The terms Warrant Officer and Officer are found in the longer term Chief Warrant Officer, causing Chief Warrant Officer John Doe to satisfy all three dictionary entries and generate three rows of results. To retain the longest term, which represents the most significant rank, you specify the consolidation settings as follows.



1. From Output column select Military Rank
2. From Method select Contained Within



Your results now include only the row Chief Warrant Officer John Doe.





 Filtering extraneous results 

An extractor sometimes produces unwanted results even though the pattern is a match. These unwanted results can often be recognized by other text near the match in the document.

To further restrict matches, create a filter.



1. On the canvas, right-click the extractor that generated the results and click Edit Output. The Output tab in Extractor Properties opens.
2. Choose to Include or Exclude results. Include is the default setting.



* An include filter is a condition that must be met for a result to be included.
* An exclude filter is a condition that must not be met for a result to be included.



3. From the first filter drop-down list, select the column that you want to apply the filter to.
4. In the next drop-down list, select the type of filter. Depending on the filter, the subsequent drop-down lists reflect the appropriate options.





 Option Description 

 length Filter according to whether the column content is shorter, longer, or equal to a specified number of characters or tokens. 
 text Filter according to whether the text matches or contains a regular expression or dictionary from the canvas, or you can enter a new regular expression. You can also set case sensitivity. 
 range Filter on the basis of specified criteria within a range of the specified column.
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. Records deletion because of retention policy does not generate. 



Event Streams can sustain high request rates, so not every request triggers an event. Instead, events are aggregated by initiator (user ID or service ID), host (IP address), operation (read, write, delete), outcome (success or failure), and topic over a 1-hour period.





 Other events 

Event Streams instances that are on the Enterprise plan automatically generate events so that you can track activity on your service.



Table 3. Event Streams events

 Action Description 

 event-streams.storage-key.read An event is created when access to the disk encryption key in Key Protect changed. If the outcome of this event is success, access to the disk encryption key is restored, and the Event Streams instance is available for use. If the outcome is failure, access to the disk encryption key was withdrawn, and the Event Streams instance is not available for use. 
 event-streams.storage-key.update The disk encryption key in Key Protect was rotated and the Event Streams instance was updated to use the new key. 
 event-streams.schema.create A schema or schema version was created or updated in the Event Streams schema registry for the enterprise instance either through the administration API or through the Confluent Serdes. 
 event-streams.schema.delete A schema or schema version was deleted from the Event Streams schema registry for the enterprise instance. 
 event-streams.schema-rule.create A new rule or global rule was created in the Event Streams schema registry for the enterprise instance. 
 event-streams.schema-rule.update An existing rule or global rule was updated in the Event Streams schema registry for the enterprise instance.
Retrieving messages via the alias queue will not trigger the interceptors on the target queue, so the message will be retrieved as it is, that is without decryption, and so it will give an accurate view on whether the message is plain text or encrypted.



1. Create an alias queue that targets to a queue

DEFINE QALIAS (DEV.QUEUE.1.ALIAS) TARGET (DEV.QUEUE.1)



* DEV.QUEUE.1.ALIAS is our name for the alias queue
* DEV.QUEUE.1 is the target queue we are using in this tutorial



![Image showing an alias queue being created](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_app_ams_crt_aliasq.png)









 Sharing public keys between alice and bob 

When a protection policy is set with encryption, it must also specify all the authorized recipients of the message. Also, the sender of that message must have the public key of those recipients in its local keystore. A policy can also specify authorized senders and this specification is enforced for messages that are signed or encrypted, in this case, receiver must have the public key of the sender to verify the identity of the message. That is, alice must have the public key of bob in their keystore and bob will need the public key of alice in their key store.

This section provides detailed steps to extract the public key for bob and add that to alice's keystore and extract the public key for alice and add that to bob's keystore.



1. Extract the public key for bob and add that to alice's keystore

On Mac:
- runmqakm -cert -extract -db /bob/.mqs/bobkey.kdb -pw passw0rd -label Bob_Cert -target bob_public.arm
In this section, you will create an alias queue which is targeted at the default queue. Once QM AMS has been enabled, the AMS interceptors will trigger when a 'put' or 'get' is performed on the default queue. Therefore, despite the fact that the messages are encrypted on the queue, the message will be readable as plain text when retrieved. In order to demonstrate that the messages are encrypted, we can use an alias queue. Retrieving messages via the alias queue will not trigger the interceptors on the default queue, so the message will be retrieved as is, without decryption, and so will give an accurate view on whether the message is plain text or encrypted.



1. Switch to the admin terminal
2. Run runmqsc to connect to your remote queue manager





* runmqsc -c -u <ADMIN_MQ_USER> -w60 <QUEUE_MANAGER_NAME>



* <ADMIN_MQ_USER> - this is 'mqUsername' in the file platformApiKey.json
* <QUEUE_MANAGER_NAME> - this is 'queueManagerName' in the file connection_info.txt
* -c informs runmqsc it should connect to a remote queue manager using the MQSERVER variable







3. The terminal will prompt you for a Password



* This is your <ADMIN_API_KEY> = 'apiKey' in the file platformApiKey.json



4. Terminal will now be waiting for input
5. Create an alias queue that targets your default queue





* DEFINE QALIAS (DEV.ALIAS.QUEUE.1) TARGET (DEV.QUEUE.1)



* DEV.ALIAS.QUEUE.1 is our name for the alias queue
* DEV.QUEUE.1 is the default queue we are using in this tutorial





!
See the [Catalog management CLI](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugincreate-filter) guidance for command options or run the ibmcloud catalog filter options command to retrieve the filter options for each filter category.







 Managing access to products for specific users by using the CLI 

Set filters at a private catalog level for fine-grained control of which products in the public catalog are available only to the users you choose.



1. Create a new filter.

ibmcloud catalog filter create [--catalog CATALOG] [--category CATEGORY] [--compliance COMPLIANCE] [--deployment-target TARGET] [--exclude-list LIST] [--include-all ALL] [--include-list LIST] [--offering-format FORMAT] [--pricing-plan PLAN] [--provider PROVIDER] [--release RELEASE] [--type TYPE]

Make sure to specify the --catalog CATALOG command option. When --catalog CATALOG is not specified, the filter is created at the account level.
2. Target an account group by specifying the command option --account-group ACCOUNT GROUP.
3. Update the filter to include or exclude a particular product or products. See the [Catalog management CLI](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugincreate-filter) guidance for command options or run the ibmcloud catalog filter options command to retrieve the filter options for each filter category.







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

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.

curl -X "PUT" "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogaccount"
-H "accept: /"
-H "Authorization: {iam-bearer-token}"
A flat list of all of the attachments in your account is displayed.

Alternatively, you can create an attachment through the Profiles page. On the Attachments tab of the profile details page, click Create and then continue with step 2.
2. Provide a name and description for your attachment. Be sure to be as descriptive as possible so that it's easy for other members of your team to understand what is being evaluated. Then, click Next.
3. Select the Profile and Profile version that you want to use for your evaluation.
4. Customize the underlying evaluations in your scan by editing the default parameters to match your specific use case.
5. Define a Scope to identify the resources that you want to evaluate and those that you want to Exclude. Then, click Next.
6. Select the frequency at which you want to evaluate your attachment.

Options include every day, every 7 days, and every 30 days. Additionally, you can now pause your scans if you need to.
7. Optional: Configure notifications.



1. If you want to receive notifications, toggle Notify me to On.
2. By default, when notifications are enabled, you are alerted when 15% or more of your controls fail in a single scan. You can change this by adjusting the Threshold percentage.

For example, if you have a profile with 100 controls and you want to be notified if 5 of them fail, you would select 5% as your threshold.
3. Select specific controls that you want to be notified about.

If there are high priority controls that pertain specifically to your job role, you might want to be notified every time that they fail. You can identify up to 15 controls per scan that you can receive individual notifications for. These notifications are sent regardless of whether the threshold that was identified in the previous step was met.



1. Click Select control.
2. Select the controls that you want to be notified about by checking the box next to the control.
3. Click Ok.





8. Review your choices and click Create.



When you create your attachment, a scan is scheduled.
Filter the keys based on the parameters. The supported key filtering parameters are



* creationDate
* deletionDate
* expirationDate
* extractable
* lastUpdateDate
* lastRotateDate
* state



The supporting operators for dates are:



* gt (greater than)
* gte (greater than or equal to)
* lt (less than)
* lte (less than or equal to)



The results will be an exact match in case any of these operators are missing.
* --key-states

The state of the keys to be retrieved. List of strings containing valid states - Active, Suspended, Deactivated, Destroyed. (default: active,suspended,deactivated).
* -l, --key-search

List keys based on search string with prepended qualifiers (e.g. exact, not, alias, name). For more details, see the [API Documentation](https://cloud.ibm.com/apidocs/key-protectkp-get-key-search-api).
* -n, --number-of-keys

Restricts the number of keys to be retrieved. The default is 200 and the maximum is 5000.
* -o, --output

Set the CLI output format. By default, all commands print in table format. To change the output format to JSON, use --output json.

Setting the output to JSON (--output json) includes the cloud resource name (CRN) in the output.
* -r, --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.
* -s, --starting-offset

Retrieves keys starting at the offset specified. The offset is zero-based, meaning offset 0 (zero) is the first key.
* -t, --key-type

The type of keys to be retrieved. If set to standard-key, standard keys will be retrieved. If set to root-key, root keys will be retrieved.
With a few exceptions, these announcements are published to the [IBM Cloud blog](https://www.ibm.com/cloud/blog/announcements).

Use the following steps to update your preferences:



1. Log in to the [IBM Privacy Preference Center](https://myibm.ibm.com/profile/dataprivacypreferences/consent/us-en) by using your IBM Cloud credentials. The toggle indicates if your entered credential is your preferred method of contact.
2. Click Next.
3. Deselect Public cloud to stop marketing communications.
4. Click Save.
You can also label sections that you want the search function to ignore. For example, you might not want to search page footers or the table of contents information. After you teach the SDU tool to recognize footers, for example, you can exclude the footer field from the index.



1. Monitor the progress of collection processing by opening the Activity tab.

Click Manage collections from the navigation panel.

Zoom

![Shows the Manage collections menu option from the navigation panel.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-activity-tab.png)

Figure 5. Manage collections menu option from the navigation panel

Click the Algorithmic Trading PDF collection tile. The collection opens to the Activity tab.
2. While you wait for the collection to be ready, open the Algo_Trading_Report_2020.pdf file that you downloaded previously.
3. Review the structure of the document.

Notice that the document consists primarily of the following structures:



* Title
* Table of contents
* Subtitles
* Text
* Footnotes
* Bibliography



4. The SDU tool has predefined labels for all but the footnotes and bibliography. You will create new field labels for these two document structures in a later procedure.



Processing is finished when the page shows that one document is available.

Zoom

![Shows the Activity page when it's ready.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-activity.png)

Figure 6. Activity page that shows the data upload is finished





 Step 4: Test your project 



1. After the crawl is completed, go to the Improve and customize page.
* Use common patterns. For example, use a(b|c|d) instead of (ab|ac|ad).
* The regular expression engine might fail if it backtracks because it can't make a negative match toward the end of the string and then attempts too many permutations. To prevent backtracks, consider using a possessive quantifier, such as (a+b)++c.



5. Click Create.
6. Choose the collection and field to search for occurrences of text that match this regular expression pattern.



In the output, the information that is extracted by the regular expression enrichment can be found under enriched_{field_name}, within the entities array.

In this example, the Facet Path is regex.cccardnumber, and the field that is selected for enrichment is text.

{
"enriched_text": [
{
"entities":
{
"path": ".regex.cccardnumber",
"type": "cccardnumber",
"text": "4000000000000000"
}
]
}
],
"text": [
"He has 2 phones, 090-1234-5678 and 080-1234-5678. His credit card number is 4000000000000000."
]
}
Show more

When you submit test queries from the Improve and customize page, you can add a facet that is based on the enriched_text.entities.model_name field. As a result, the cccardnumber regular expression enrichment that you created is displayed as a facet value by which documents can be filtered. For more information about creating facets, see [Adding facets](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-facetsfacetexist).



 Regular expression limits 

The number of regular expressions that you can define per service instance depends on your Discovery plan type.



Regular expression plan details

 Plan Regular expressions per service instance 

 Cloud Pak for Data Unlimited 
 Premium 100 
 Enterprise 100