vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If you want to specify a default rule for all metrics that are not processed by other rules, you would specify the rule ("locations" : [""]) as the final rule in your rules definition for the route.
* If metrics data doesn't match any rule and no default target is configured, the metrics are dropped and not routed to any target.
* Any update to 1 or more rules in a route definition discards the existing rule set and replaces it with the specified configuration. When you update a route, you must define all existing rules in the rule set that do not change and add the changes to the rules that must be updated.
* Information about routes is stored as metadata in the primary location that you have set for the IBM Cloud account.

If you do not configure a primary metadata location, the location is set to the location where you define your first target in the account. For more information, see [Configuring account settings](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-settings).
* You can use private and public endpoints to manage routes. For more information about the list of ENDPOINTS that are available, see [Endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints).



* You can manage routes from the private network by using an API endpoint with the following format: https://private.REGION.metrics-router.cloud.ibm.com
* You can manage routes from the public network by using an API endpoint with the following format: https://REGION.metrics-router.cloud.ibm.com
* You can disable the public endpoints by updating the account settings. For more information, see [Enforcing private endpoints](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-endpoints-enforce-private).



* The route name must be 1000 characters or less and cannot include any special characters other than space, dash -, dot ., underscore _, and colon :.

The name must not include any personal identifying information (PII).
Authentication 

The IBM Cloud® Data Engine service is tightly integrated with IBM Cloud® Identity and Access Management (IAM). In order to perform an action by using the Data Engine user interface or API, you require an IAM user ID, which is an IBMid with an IBM Cloud account. Data Engine then verifies whether you are authorized to work with the service instance.



 Cloud Identity and Access Management (IAM) session support 

The Data Engine UI supports [IAM sessions](https://cloud.ibm.com/docs/account?topic=account-iam-work-sessions). If you limit the duration of active sessions, the authentication of the UI will stop after the session expires, so you cannot submit new queries or retrieve result data until you reload the page and reauthenticate. Result data that is already cached in the browser remains visible. If you terminate an active IAM session before it expires, the Data Engine UI remains authenticated for the leftover lifetime of the current access token, which can up to 20 minutes.

Queries that are submitted from the UI can run at maximum for 1 hour or the remaining session lifetime, whichever is shorter. Queries that are submitted through the API can always run for 1 hour maximum if you retrieve the API token by using the method described in the [Data Engine API documentation](https://cloud.ibm.com/apidocs/sql-query-v3).





 Authenticating access to data resources in Data Engine 



 SSO through Cloud Identity and Access Management 

IAM is also the preferred and the default mechanism for authenticating access to downstream data resources that are referenced by your SQL queries. If you use IAM, ensure that the user ID that you use to submit the SQL query through the web console or the API is authorized to read the input locations (referenced in the FROM clauses of the query), and to write the result set to the target location (referenced in the INTO clause of the query). This mechanism provides seamless single sign-on (SSO) for your query submissions in Data Engine. You can use the following alternative methods for authenticating access to data resources:



 IBM Cloud service credentials
(https://cloud.ibm.com/docs-content/v1/content/adc643f3bedeea02b638bc1c34732852dcb40a45/openwhisk/images/composer-conditional.png)

Figure 3. Sequence with conditional branching







 Loops in Composer 

You can create looping constructs in Composer. In this example, action2 executes as long as action1 returns true. Composer limits the total number of steps you can execute in a composed sequence. The current limit is 20.



 For JavaScript 

const composer = require('@ibm-functions/composer')

module.exports = composer.while('action1', 'action2')





 For Python 

import composer

def main():
return composer.loop('action1', 'action2')

Zoom

![Sequence with while loop.](https://cloud.ibm.com/docs-content/v1/content/adc643f3bedeea02b638bc1c34732852dcb40a45/openwhisk/images/composer-loop.png)

Figure 4. Sequence with while loop







 Inline definition of Actions within a composition 

You can define actions within the composition code itself. In this example, you create the action definition inline with the composition that is named hello by using the composer.action().



 For JavaScript 

const composer = require('@ibm-functions/composer')

module.exports = composer.seq('action1',
composer.action('hello', {
action: function () { return { message: 'Hello!' } }
}))





 For Python 

import composer

def hello(args):
return { 'message': 'hello' }

def main():
return composer.sequence(
'action1',
composer.action('hello', hello)
)

Zoom

![Sequence with inline action definition.]
[View Node OU status on MSP tile](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/msp-nodeou.png)

Figure 3. View Node OU status on MSP tile
2. Click the Settings icon for the MSP. The checkbox to add Node OU is selected by default. You do not have to add a new JSON file, you can simply click Update MSP definition to enable Node OU support for the MSP.

Zoom

![Node OU checkbox](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/nodeou-checkbox.png)

Figure 4. Node OU checkbox



The MSP is also automatically updated on any peer or ordering nodes that are configured to use this MSP. There is a brief downtime when the node is automatically restarted to use the updated MSP.





 Part two: Enable Node OU support for the MSP on a channel 



1. Open the Channels tab, select the channel that you want to update and click Channel details.
2. Scroll down and click the channel member MSP definition that you just enabled Node OU support for. The checkbox to enable Node OU support is selected by default.
3. Select the existing MSP definition and the associated identity and click Update MSP definition.



Because you likely still have admin certificates in the MSP that will expire, you still need to follow the manual steps in this topic to update them. But after you complete that process, you do not have to follow the manual steps again next year after the certificates expire, since you have now enabled the Node OU support on the MSP.







 Certificate renewal and expiration 

By default, most certificates that are generated by IBM Blockchain Platform CAs expire after one year.
Provisioning a virtual server 

You can use the Hyper Protect Virtual Servers service to create a virtual server from the IBM Cloud UI or from the CLI.

You can use an IBM-provided image or your own image to provision a server.

Use the CLI to provision a server if you want to:



* [Use your own image](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-byoi). You need to create an image file and registration definition file as described [here](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-byoi).
* [Create servers](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hpvs-cli-plugin-hpvs_cli_plugincreate_instance) without a public inbound address.



Do not use personal information, for example, your name, as the instance name or as part of the instance name. The data that you provide when you provision an instance or interact with the hpvs cli is not considered to be personal data or credentials. Learn more about IBM Cloud Hyper Protect Virtual Servers' Data usage and Certifications [here](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=165C6EF0FFDA11E8BABD512A6952EE1F).

The Ubuntu servers are preconfigured in such a way that the passwords expire after 90 days. After the user password expires, you have 30 days to change your password. If you don't change your password within the 30 days, your account becomes inactive and it is no longer possible to log in thru SSH even if you are using SSH-keys. For information, see [Protecting a virtual server](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-protect_vs).
Therefore the host_url would be https://d0ddb7-optools.uss02.blockchain.cloud.ibm.com.
* fabric_node_OUs: Fabric-specific Organization Units (OUs) that enable identity classification. NodeOUs contain information for how to distinguish clients, peers, and orderers based on their OU. If the check is enforced, by setting Enabled to true, the MSP considers an identity valid only if it is an identity of type client, a peer, an admin, or an orderer. An identity should have only one of these special OUs, which are assigned to an identity when it is registered with the CA. See this topic for an example of [how to specify the fabric_node_OU in an MSP](https://hyperledger-fabric.readthedocs.io/en/v2.2.0/discovery-cli.htmlconfiguration-query) in the Fabric Service Discovery documentation. Or learn more about using [Node OUs](https://hyperledger-fabric.readthedocs.io/en/v2.2.0/membership/membership.htmlnode-ou-roles-and-msps) in Fabric.



The following additional fields are also available in your MSP definition but are not required:



* intermediate_certs: (if an intermediate CA was used) Paste in an array that contains one or more certificates from the external intermediate CA in base64 format. You must provide either a CA root certificate or an intermediate CA certificate, you can also provide both.
* tls_intermediate_certs: (if an intermediate TLS CA was used) Paste in an array that contains one or more certificates from the intermediate TLS CA in base64 format. You must provide either an external TLS CA root certificate or an external intermediate TLS CA certificate, you can also provide both.
* organizational_unit_identifiers: A list of Organizational Units (OU) that valid members of this MSP should include in their X.509 certificate. This is an optional configuration parameter that is used when multiple organizations leverage the same root of trust and intermediate CAs, and they have reserved an OU field for their members.
You can configure whether you want to use private endpoints only, location of the metadata that is required by the service to run, default destinations in case you do not set a rule for a region where you operate, and more.

Before you can configure the resources that define how to manage metrics in the account, you must define a Primary metadata region. The Primary metadata region defines the location where metadata about your account and resources is stored. You can optionally configure a Backup metadata region. Metadata includes information about the routing rules, the account settings that define how to manage metrics in your account, and target details, including credentials that are needed to send the data to your destinations. The setting definition is a global resource that defines the account values that are used by the IBM Cloud Metrics Routing service to route metrics to your destinations..

After you configure the primary metadata region, you must create 1 or more targets, and 1 or more routes.



* A target defines a destination where you want to route metrics and store them for further analysis. A target resource definition is a regional resource. However, some of the target's details are required in the account's primary and backup metadata locations for operational purposes.
* A route defines the rules on how to route metrics across the account to your destinations (targets). A route resource definition is a global resource that defines rules whose scope goemight go beyond a region.



In your account, metrics are automatically collected from IBM Cloud services that run in the account, with the exception of some services that require additional configuration to enable metrics. For more information about services that generate metrics, see [Cloud services](https://cloud.ibm.com/docs/metrics-router?topic=metrics-router-cloud_services).

After you configure IBM Cloud Metrics Routing in your account, metrics are routed to the target of your choice. You are responsible for managing the metrics in the target resources.

All data and the configuration that is required for the IBM Cloud Metrics Routing service deployment is retained within the region in which it is hosted.

The IBM Cloud Metrics Routing's metadata in your account is hosted in the primary metadata location and the backup metadata location.
If you haven't already created a channel and joined at least one peer to it, see the [Build a network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-networkibp-console-build-network-structure) tutorial for instructions.

If you are creating a new channel, ensure that you select Advanced channel configuration so that you have the opportunity to specify the Channel Application Capability 2.0.0 or higher.





 Export and Import Membership Service Providers (MSPs) 

A benefit of the decentralized nature of smart contract lifecycle governance is that channel members can agree upon which organizations on the channel and how many of them are required to approve a smart contract definition before it can be committed to a channel. This agreement is described in the channel "lifecycle endorsement policy" when the channel is created. Because an approval notification is sent to each organization in the policy, the console requires the endpoint address of each organization, which happens to be included in their MSP. Therefore, each organization that is specified in the lifecycle endorsement policy must export their MSP and send it to the other members in the policy. And then each member must import the MSP from each organization into their console. These import and exports steps should have already happened, before the organization peers joined the channel. See [Importing an MSP](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-import-nodesibp-console-import-msp) for more details.





 Peer admin identity 

Because only peer admin identities are allowed to install a smart contract on a peer, if you plan to propose a smart contract definition, you need to have the peer admin identity in your console wallet. The peer admin identity is generated when the peer organization MSP is created and it is associated with the peer node during node deployment. If you are unsure, open the peer tile, and in the left column, view the name of the admin identity under Associated identity for peer. That is the identity that must be in your wallet and is required when you propose a smart contract definition.







 Limitations 



 Can I continue to use the Fabric SDK to deploy my smart contracts?
This features can help you to plan for activities such as scheduling maintenance windows during the least used times and identifying the busiest times when high activity might cause users to report query result delays or performance concerns.





 Query runtime distribution 

The query runtime distribution chart displays a relative duration of a query over time.





 Sessions 

The sessions chart displays the number of connections over time. You can also view the list of sessions, change priority, stop transactions, or stop sessions.





 Current GRA distribution 

The current GRA distribution chart displays information about the current guaranteed resource allocation share of resource groups.







 Workload 

On the Workload page, you can view graphs for the following items:



* Queue monitor
* Resource allocation
* Current resource allocation
* CPU utilization
* Disk utilization





 Queue monitor 

The queue monitor chart summarizes the short and long queues on the system and how busy they are. The report shows you the number of snippets in the snippet queues and the number of jobs in the GRA queues.

Thee chart shows the values for the latest sample of data:



* The number of long GRA jobs that are waiting for GRA resources.
* The number of short GRA jobs that are waiting for GRA scheduler slots.
* The number of long snippets that are waiting for resources.
* The number of short snippets that are waiting for resources.



The queue sizes monitor trend chart displays the recent history of these four queues. For newly added hosts, the charts show a short sample of trend, but the charts can grow to show up to six days of trend.

You can zoom in and out by moving the slider to see a specific range. You can also expand your graph view by clicking the arrows icon.

Netezza Performance Server separates short queries from longer-running queries. Short queries are those queries that run in two seconds or less. For “lightly loaded” systems, the queues might be zero if no queries are waiting, or small. As the system becomes busy with concurrent short or long queries, these queues can show a larger number of waiting snippets and jobs.
For information about the environment properties and resources that are available by default in pipeline environments, see [Environment properties and resources](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-deliverypipeline_environmentdeliverypipeline_environment).
* Can I use the IBM Cloud CLI to run a pipeline stage?

You can use the IBM Cloud developer tools CLI plug-in to run a pipeline stage.



1. [Install the IBM Cloud developer tools CLI plug-in](https://cloud.ibm.com/docs/cli?topic=cli-install-devtools-manually).
2. From the command line, run the following command to manually start your pipeline:

ibmcloud dev pipeline-run pipelineID --stage-id stageID



For more information about the pipeline-run command, see [pipeline-run](https://cloud.ibm.com/docs/cli?topic=cli-idt-clipipeline-run).
* Can I download the yaml file for a delivery pipeline?

You can export the definition for an entire pipeline by appending /yaml to the pipeline URL. For more information about exporting the definition for an entire pipeline, see [Modifying, exporting, and deleting Continuous Delivery pipeline data](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-cd_personal_datamanaging_pipeline_data).
* Can I manage delivery pipelines by using Terraform?

You can use Terraform to provision, update, and de-provision Tekton pipelines, definitions, properties, triggers, and trigger properties. For more information about using Terraform with Tekton pipelines, see [Working with Tekton pipelines](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tekton-pipelines), and the [ibm_cd_tekton_pipeline resources documentation](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/cd_tekton_pipeline).
(https://cloud.ibm.com/docs/containers?topic=containers-plan_deployvariables)
* [How can I make sure that my app has the correct resources?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployresources)
* [How can I add capabilities to my app configuration?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploycapabilities)
* [How can I add IBM services to my app, such as Watson?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployservices_ibm)



* [Planning highly available deployments](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployhighly_available_apps)



* [How can I increase the availability of my app?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployincrease_availability)
* [How can I scale my app?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployscale)



* [Versioning and updating apps](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployupdating)



* [How can I organize my deployments to make them easier to update and manage?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploydeploy_organize)
* [What app update strategies can I use?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployupdating_apps_strategy)
* [How can I automate my app deployment?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploypackaging)



* [Setting up service discovery](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployservice_discovery)
* [How can I scale my app?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployscale)



* [Versioning and updating apps](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployupdating)



* [How can I organize my deployments to make them easier to update and manage?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploydeploy_organize)
* [What app update strategies can I use?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployupdating_apps_strategy)
* [How can I automate my app deployment?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploypackaging)



* [Setting up service discovery](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployservice_discovery)



* [How can I make sure that my services are connected to the correct deployments and ready to go?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployservices_connected)
* [How can I expose my services on the Internet?](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployservices_expose_apps)



* [Securing apps](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deploysecure_apps)
* [Managing access and monitoring app health](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployapp_plan_logmet)



* [How can I control who has access to my app deployments?]
(https://cloud.ibm.com/docs/containers?topic=containers-plan_deployupdating_apps_strategy)
* [How can I automate my app deployment?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploypackaging)



* [Setting up service discovery](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployservice_discovery)



* [How can I make sure that my services are connected to the correct deployments and ready to go?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployservices_connected)
* [How can I expose my services on the Internet?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployservices_expose_apps)



* [Securing apps](https://cloud.ibm.com/docs/containers?topic=containers-plan_deploysecure_apps)
* [Managing access and monitoring app health](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployapp_plan_logmet)



* [How can I control who has access to my app deployments?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployapp_plan_logmet_access)
* [After I deploy my app, how can I monitor its health?](https://cloud.ibm.com/docs/containers?topic=containers-plan_deployapp_plan_logmet_monitor)





[Building containers from images](https://cloud.ibm.com/docs/containers?topic=containers-imagesimages)



* [Deploying containers from an IBM Cloud Container Registry image to the default Kubernetes namespace](https://cloud.ibm.com/docs/containers?topic=containers-imagesnamespace)