vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Click View all in the Resource summary section of the dashboard.
3. In the Services section, click the IBM Cloud instance that you plan to monitor.

The IBM Cloud UI Manage page opens.
4. Click Actions > Add monitoring to configure platform metrics in the region of your IBM Cloud instance.

If the menu choices include the Monitoring option, then your instance is already configured for platform metrics.

Zoom

![If the Actions menu includes monitoring items, then your instance is already configured for platform metrics.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/images/monitoring_add.png)

Figure 1. Monitoring menu
5. Provision an instance of the IBM Cloud Monitoring service.

After you provision the Monitoring instance, the Observability page opens. To continue working with IBM Cloud, go back to the IBM Cloud UI.







 Viewing metrics 

To monitor IBM Cloudant metrics, you must launch the IBM Cloud Monitoring web UI instance that is enabled for platform metrics in the region where your IBM Cloud instance is available.

You can use different options to launch the IBM Cloud Monitoring web UI and monitor metrics that are described in the following section.



 Launching IBM Cloud Monitoring web UI from the IBM Cloudant Dashboard 

Complete the following steps to launch the IBM Cloud Monitoring web UI from the IBM Cloud Dashboard:



1. Log in to IBM Cloud.

The IBM Cloud Dashboard opens.
2. Click View all in the Resource summary section of the dashboard.
3. In the Services section, click the IBM Cloudant instance that you plan to monitor.

The IBM Cloudant Manage page opens.
4. Click Actions, and select Monitoring.

Zoom

![If the Actions menu includes monitoring items, then your instance is already configured for platform metrics.]
For more information, see [Updating the master](https://cloud.ibm.com/docs/containers?topic=containers-updatemaster) and [worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-updateworker_node).







 Making your resources highly available 

While no system is entirely failsafe, you can take steps to increase the high availability of your apps and services in Red Hat OpenShift on IBM Cloud.

Review more information about making resources highly available.



* [Reduce potential points of failure](https://cloud.ibm.com/docs/openshift?topic=openshift-haha).
* [Create multizone clusters](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clustersha_clusters).
* [Plan highly available deployments](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployhighly_available_apps) that use features such as replica sets and pod anti-affinity across multizones.
* [Run containers that are based on images in a cloud-based public registry](https://cloud.ibm.com/docs/openshift?topic=openshift-images).
* [Plan data storage](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-plan). Especially for multizone clusters, consider using a cloud service such as [IBM Cloudant](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-getting-started-with-cloudant) or [IBM Cloud Object Storage](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-getting-started-cloud-object-storage).
For this example, create an IBM Cloudant service instance in the CodeEngine_servicebindings_resource group resource group.



4. Add the my-user user to this access group.
5. Create a service ID for the service instance that you want to bind to.



1. Launch [Access (IAM) Overview](https://cloud.ibm.com/iam/overview).
2. Select Manage > Access(IAM) > Service IDs.
3. Create a service ID; for example, CodeEngine_servicebindings_serviceid.
4. From within this new service ID, click the Assign group. From the Assign access page, select Access policy. Do not select Access groups. Assign the following access policy,



* For Service, select the service instance that you want to bind to; for example, IBM Cloudant service instance.
* For Resources, select the specific resource group that you created for users that can create service bindings to this service.
* For Resource group access, select Viewer.
* For Roles and actions, select Service access of Manager and Platform access of Operator.
* Click Add to add the access policy to this service ID.



5. Click Assign to assign the access policies to this service ID.





Now that you have a custom service ID for service bindings, you must configure your Code Engine project to use the custom service ID.





 Configuring a project to use a custom service ID 

To configure a Code Engine project for service binding to use a custom service ID that you manage, use the [ibmcloud ce project update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-update) CLI command and specify the --binding-service-id option. You can update your project to use a custom service ID only with the CLI.

The project update command works within the project that is selected as the current context. Before you use the project update command, confirm that you are in the desired project.
Store them in a [credentials file](https://cloud.ibm.com/apidocs/cloudant?code=goauthentication-with-external-configuration). As an alternative to ibmcloud login, you can set the environment variable DATA_VIRTUALIZATION_APIKEY to an IAM API key.

IBM Cloud CLI requires Java&trade 1.8.0. You can download the CLI from IBM Cloud to use on your local system as a complement to the IBM Cloud console.





 Data sources 

Connect data sources to the watson query service.



 ibmcloud watson-query datasource-connections 

Gets all data source connections that are connected to the service.

ibmcloud watson-query datasource-connections



 Examples 

Get data connections

ibmcloud watson-query datasource-connections





 Example output 

{
"datasource_connections" : [ {
"agent_class" : "F",
"dscount" : "0",
"hostname" : "dv-0.dv.tns.svc.cluster.local",
"is_docker" : "N",
"node_name" : "AdminNode",
"node_description" : "Not specified",
"port" : "6414",
"os_user" : "bigsql",
"data_sources" : {
"cid" : "MSSQL10000",
"dbname" : "mssql2014db1",
"connection_id" : "75e4d01b-7417-4abc-b267-8ffb393fb970",
"srchostname" : "example.ibm.com",
"srcport" : "1433",
"srctype" : "MSSQLServer",
"status" : "string",
"usr" : "DV-user",
"uri" : "example.ibm.com:1433/"
} ]
} ]
}
(https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/img0011.png)

Figure 1. IBM Cloudant instances in resource list
3. Click the Revoke button under the Cloudant credentials status section. If you do not see the information that is shown in the next screen capture, the credential was already revoked, or it never existed.

Zoom

![Revoke instance URL style credential.](https://cloud.ibm.com/docs-content/v1/content/522c6f62358b063f921283400a601c3f9bc66f08/Cloudant/tutorials/images/revoke-creds-status.png)

Figure 2. Instance URL style credential
4. Click OK to confirm your action on the dialog window to proceed.
5. When the operation completes successfully, the status changes to Revoked.



After the credential is revoked by using this process, the Cloudant credentials status section no longer appears on the page.
Getting Started 

This tutorial is a short introduction to using an IBM Cloud® Databases for etcd deployment.



 Before you begin 



* You need to have an [IBM Cloud account](https://cloud.ibm.com/registration).
* You also need a Databases for etcd deployment. You can provision one from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/databases-for-etcd). Give your deployment a memorable name that appears in your account's Resource List.
* [Set the Root Password](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-root-password) for your deployment.
* Review the [Getting to production](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-best-practices) documentation for general guidance on setting up a basic IBM Cloud® Databases for etcd deployment.







 Step 1: Connect with etcdctletcdctl 

Download and install etcdctl, from the [the coreos/etcd repository](https://github.com/coreos/etcd/releases/latest). Once it is installed, get the formatted connection strings from your deployment's Dashboard Overview, in Endpoints. The CLI tab contains information that a CLI client uses to make a connection to your deployment.

Zoom

![Endpoints panel](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/images/getting-started-endpoints-panel.png)

Figure 1. Endpoints panel

First, download (or save the contents of) the TLS certificate to a file and name the file with the TLS certificate name. Either save it to the location where you plan on running the etcdctl commands or remember where the file is saved so you can provide its full path to the environment variable.
import com.ibm.cloud.cloudant.v1.model.DocumentResult;
import com.ibm.cloud.cloudant.v1.model.PutReplicationDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.ReplicationDatabase;
import com.ibm.cloud.cloudant.v1.model.ReplicationDatabaseAuth;
import com.ibm.cloud.cloudant.v1.model.ReplicationDatabaseAuthIam;
import com.ibm.cloud.cloudant.v1.model.ReplicationDocument;

Cloudant service = Cloudant.newInstance();

ReplicationDatabase sourceDb = new ReplicationDatabase.Builder()
.url("<your-source-service-url>/source")
.build();

ReplicationDatabaseAuthIam targetAuthIam =
new ReplicationDatabaseAuthIam.Builder()
.apiKey("<your-iam-api-key>")
.build();

ReplicationDatabaseAuth targetAuth = new ReplicationDatabaseAuth.Builder()
.iam(targetAuthIam)
.build();

ReplicationDatabase targetDb = new ReplicationDatabase.Builder()
.auth(targetAuth)
.url("<your-target-service-url>/target"))
.build();

ReplicationDocument replDocument = new ReplicationDocument();
replDocument.setSource(sourceDb);
replDocument.setTarget(targetDb);
replDocument.setFilter("mydesigndoc/myfilter");

Map queryParams = new HashMap<>();
queryParams.put("foo", "bar");
queryParams.put("baz", 5);
replDocument.setQueryParams(queryParams);
Release notes for Qiskit Runtime 

Use these release notes to learn about the latest updates to Qiskit Runtime.



  13 January 2023 

The Standard plan now includes access to simulators.





  19 October 2022 

The Estimator and Sampler primitives interface is redesigned.





  12 April 2022 

Qiskit Runtime achieves Beta maturity in IBM Cloud, and introduces pay-as-you-go for the standard plan.





  15 February 2022 

Initial release of primitive programs.





  31 January 2022 

You can run jobs on both physical quantum devices, as well as quantum device simulators. New API endpoints have been added to allow you to view device information. There is a free plan as well as a lite plan, to allow access to simulators or physical quantum devices. If you do not specify a device for your job to run on, the job will be sent to the least busy system or simulator that you have access to.





  27 November 2021 

Introducing Qiskit Runtime (internal-only). Get a glimpse of the quantum computing future with our world-leading Qiskit Runtime, a new architecture that delivers significant performance enhancements to program execution. Our physical systems and simulators (cloud-based classical emulators of quantum systems) now enable you to experience frictionless quantum computing; that is, the ability to execute quantum programs in an environment where the classical computer is physically closer to the quantum computer. Test programs and algorithms, and develop new models with our cloud-based quantum runtime for drastically improved capacity and higher performance today.
For example, if you choose the Lite plan, data is not stored at all. However, if you choose the 7-day plan, data is stored for 7 days and you have access to it through the logging Web UI.







 Data archives 

You can archive logs from an IBM Log Analysis instance into a bucket in an IBM Cloud Object Storage (COS) instance. [Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-archiving).

When data is archived, data going from logging to IBM Cloud Object Storage (COS) is encrypted in transit over HTTPS.

You must configure archiving to a COS instance if you want to backup your logs for long term storage.

You can use the Data Engine service to query data in archive files that are stored in an Object Storage (COS) bucket in your account. You can run queries from the IBM Cloud UI, or programmatically.





 Data exports 

You can export data in JSONL format locally, write data to your terminal, or request an email with a link to the data. [Learn more](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-export).

Consider the following information when you export log data:



* You export a set of log entries. To define the set of data that you want to export, you can apply filter and searches. You can also specify the time range.
* From the Web UI, when you export logs, you get an email that is sent to your email address, with a link to a compressed file that includes the data. To get the data, you must click the link and download the compressed file. Notice that the link expires automatically after 12 hours. The compressed file is hosted in IBM Cloud Object Storage (COS).
* When you export logs programmatically, you can choose to send an email, or to write data to the terminal.
* When you export logs, you have a limit of lines that you can export in a request. You can specify to export older lines or newer lines in case you reach the limit in the time range that you specify for the export.
ibmcloud cra terraform-validate --tf-plan TFPLANFILE --report REPORT [--format FORMAT] [--policy-file POLICYFILE] [--quiet] [--region REGION] [--state-file STATEFILE] [--strict] [--toolchainid TOOLCHAINID] [--verbose] [--sccv2] [--attachment-file ATTACHMENT_FILE]

ibmcloud cra tf -r report-user-profile.json -t ./tfplan.json -p ./user-profile.json --verbose



 Example Terraform plan file for the terraform-validate command 

{
"format_version": "0.2",
"terraform_version": "1.0.2",
"planned_values": {
"root_module": {
"child_modules": [
{
"resources":
{
"address": "module.instance.ibm_resource_instance.cos_instance",
"mode": "managed",
"type": "ibm_resource_instance",
"name": "cos_instance",
"provider_name": "registry.terraform.io/ibm-cloud/ibm",
"schema_version": 0,
"values": {
"location": "global",
"parameters": null,
"plan": "lite",
"service": "cloud-object-storage",
"timeouts": null
},
"sensitive_values": {
"extensions": {},
"last_operation": {},
"plan_history": ],
"tags": ]
}
}
],
"address": "module.instance"
},
{
"resources":
{
Resource list with a virtual server that shows one server that is being provisioned (Inactive) and one server that is already provisioned (Active)" caption-side="bottom"}





 Creating a virtual server from the CLI 

To create a virtual server from the CLI, you must first install the [CLI](https://cloud.ibm.com/docs/hpvs-cli-plugin), then run the following command:

ibmcloud hpvs instance-create NAME PLAN LOCATION [--hostname HOST-NAME] [(--ssh SSH-KEY | --ssh-path SSH-KEY-PATH)] [(--rd REGISTRATION-DEFINITION | --rd-path REGISTRATION-DEFINITION-PATH)] [-i IMAGE-TAG] [-e ENV-CONFIG1 -e ENV-CONFIG2 ...] [-g RESOURCE-GROUP-ID] [-t TAG1 -t TAG2 ...] [--outbound-only]

Where:

NAME
: Is the name of your new instance.

PLAN
: Is the name or ID of your service plan, for example, the plan name for a free plan is lite-s. The possible values for plan name are: lite-s, entry, small, and medium.

LOCATION
: Is the target location to create the service instance. The possible values are: dal10, dal12, dal13, fra02, fra04, fra05, syd01, syd04, syd05, wdc04, wdc06, wdc07.



 Command options 

--hostname HOST-NAME
: The hostname that will be set within the Hyper Protect Virtual Servers container by using this parameter value.

--ssh SSH-KEY
: Public half of the SSH key to access the virtual server later. --ssh or --ssh-path is required when you use an IBM-provided image.

--ssh-path SSH-KEY-PATH
: File path to the file that contains the public half of the SSH key to access the virtual server later.
For more information about IAM, see [Authenticating to Watson services](/docs/watson?topic=watson-iam).

New network and data security features : Support for data encryption with customer-managed keys - Users of new premium and dedicated instances can integrate IBM® Key Protect for IBM Cloud® with Discovery to encrypt their data and manage encryption keys. For more information, see [Protecting sensitive information in your Watson service](https://cloud.ibm.com/docs/discovery?topic=watson-keyservice). : Support for private network endpoints - Users of Premium plans can create private network endpoints to connect to Discovery over a private network. Connections to private network endpoints do not require public internet access. For more information, see [Public and private network endpoints](https://cloud.ibm.com/docs/discovery?topic=watson-public-private-endpoints).





 6 December 2019 

Known issue for Lite plan crawl status : If your Lite plan reaches the document limit of the environment, any running crawls do not progress any further. The displayed crawl status changes to not_configured.





 11 October 2019 

New Seoul location now available : You can now create Discovery instances in the Seoul data center. Like all locations, the IBM Cloud® Seoul location (seo) uses token-based Identity and Access Management (IAM) authentication. The following features are not available in the Seoul data center: IBM Watson™ Discovery News, connectors, custom stopwords, and Japanese tokenization dictionaries.





 30 September 2019 

Deprecated Knowledge Graph Beta APIs and Knowledge Graph relationship query : As announced [3 September 2019](https://cloud.ibm.com/docs/discovery?topic=discovery-release-notes3sept19), the IBM Watson™ Discovery Knowledge Graph Beta APIs (Knowledge graph entity query /v1/environments/{environment_id}/collections/{collection_id}/query_entities and Knowledge Graph relationship query /v1/environments/{environment_id}/collections/{collection_id}/query_relations) are no longer accessible.
"resource_plan_id": "bb0005a1-ec13-4ee4-86f4-0c3b15a357d5",
"public_ip": "52.116.29.73",
"internal_ip": "172.17.151.218",
"storage": 53687091200,
"memory": 2147483648,
"vcpu": 1,
"image_type": "self-provided",
"image_os": "self-defined",
"image_name": "de.icr.io/hpvs_test/ubuntu:v2",
"free_time_left": 2156814134,
"environment": {
"TEST_VAR": "value",
"TEST_VAR2": "value2"
},
"last_operation": "update succeeded"
}
Show more







 hpvs instance-create 

This command creates a new Hyper Protect Virtual Servers instance.

ibmcloud hpvs instance-create NAME PLAN LOCATION [--hostname HOST-NAME] [(--ssh SSH-KEY | --ssh-path SSH-KEY-PATH)] [(--rd REGISTRATION-DEFINITION | --rd-path REGISTRATION-DEFINITION-PATH)] [-i IMAGE-TAG] [-e ENV-CONFIG1 -e ENV-CONFIG2 ...] [-g RESOURCE-GROUP-ID] [-t TAG1 -t TAG2 ...] [--outbound-only]

NAME
: The name of your new instance.

PLAN
: The pricing plan ID or plan name for your Hyper Protect Virtual Server instance, for example, the plan name lite-s or its corresponding plan ID bb0005a1-ec13-4ee4-86f4-0c3b15a357d5. To list all plans and IDs, run the ibmcloud catalog service hpvs command.

LOCATION
: The location ID to deploy your Hyper Protect Virtual Server instance to.
cos_cli = ibm_boto3.client("s3",
ibm_api_key_id=COS_API_KEY_ID,
ibm_service_instance_id=COS_SERVICE_CRN,
config=Config(signature_version="oauth"),
endpoint_url=COS_ENDPOINT)

more_results = True
next_token = ""

while (more_results):
response = cos_cli.list_objects_v2(Bucket=bucket_name, MaxKeys=max_keys, ContinuationToken=next_token)
files = response["Contents"]
for file in files:
print("Item: {0} ({1} bytes).".format(file["Key"], file["Size"]))

if (response["IsTruncated"]):
next_token = response["NextContinuationToken"]
print("...More results in next batch!n")
else:
more_results = False
next_token = ""

except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to retrieve bucket contents: {0}".format(e))
Show more

SDK References



* Classes



* [S3.Client](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlclient)



* Methods



* [list_objects_v2](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.Client.list_objects_v2)











 Using Key Protect 

Key Protect can be added to a storage bucket to encrypt sensitive data at rest in the cloud.



 Before You Begin 

The following items are necessary in order to create a bucket with Key-Protect enabled:
buckets = cos.buckets.all()
for bucket in buckets:
print("Bucket Name: {0}".format(bucket.name))
except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to retrieve list buckets: {0}".format(e))

SDK References



* Classes



* [Bucket](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlbucket)
* [ServiceResource](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlservice-resource)



* Collections



* [buckets](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlS3.ServiceResource.buckets)









 List items in a bucket 

def get_bucket_contents(bucket_name):
print("Retrieving bucket contents from: {0}".format(bucket_name))
try:
files = cos.Bucket(bucket_name).objects.all()
for file in files:
print("Item: {0} ({1} bytes).".format(file.key, file.size))
except ClientError as be:
print("CLIENT ERROR: {0}n".format(be))
except Exception as e:
print("Unable to retrieve bucket contents: {0}".format(e))

SDK References



* Classes



* [Bucket](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlbucket)
* [ObjectSummary](https://ibm.github.io/ibm-cos-sdk-python/reference/services/s3.htmlobjectsummary)



* Collections
See the following example request to retrieve the current consumption of capacity:



* Curl
* Java
* Node
* Python
* Go



curl "$SERVICE_URL/_api/v2/user/current/throughput"

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.CurrentThroughputInformation;

Cloudant service = Cloudant.newInstance();

CurrentThroughputInformation response =
service.getCurrentThroughputInformation().execute().getResult();

System.out.println(response);

const { CloudantV1 } = require('@ibm-cloud/cloudant');

const service = CloudantV1.newInstance({});

service.getCurrentThroughputInformation().then(response => {
console.log(response.result);
});

from ibmcloudant.cloudant_v1 import CloudantV1

service = CloudantV1.new_instance()

response = service.get_current_throughput_information().get_result()

print(response)

getCurrentThroughputInformationOptions := service.NewGetCurrentThroughputInformationOptions()

currentThroughputInformation, response, err := service.GetCurrentThroughputInformation(getCurrentThroughputInformationOptions)
if err != nil {
panic(err)
}

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

The previous Go example requires the following import block:

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