vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Monitoring Integration 

Monitoring for IBM Cloud® Databases for MySQL deployments is provided through integration with the IBM Cloud® Monitoring Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for MySQL dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/99dae60bd0de1987ffcce4822e29b2bcdefe3a43/databases-for-mysql/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/99dae60bd0de1987ffcce4822e29b2bcdefe3a43/databases-for-mysql/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard in monitoring



 Monitoring Availability 

IBM Cloud Monitoring monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.

If you have deployments that are in Single-zone Region (SZR) - che01 then your logs are forwarded to a IBM Cloud Monitoring instance in another region.
Monitoring Integration 

Monitoring for IBM Cloud® Databases for EnterpriseDB deployments is provided through integration with the IBM Cloud® Monitoring Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for EnterpriseDB dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

The default dashboards are not shown until database instances begin emitting metrics.

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/e2b18e1112dc55facb736744a935365dce13849a/databases-for-enterprisedb/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/e2b18e1112dc55facb736744a935365dce13849a/databases-for-enterprisedb/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard in monitoring



 Monitoring Availability 

IBM Cloud Monitoring monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.
Monitoring Integration 

Monitoring for IBM Cloud® Databases for etcd deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward select information so you can monitor deployment health and resource usage. To see your Databases for etcd dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/images/monitoring-ui-link.png)

Figure 1. The Monitoring link in a deployment

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard in monitoring



 Monitoring Availability 

IBM Cloud Monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.

If you have deployments that are in Single-zone Region (SZR) che01 then your logs are forwarded to a monitoring instance in another region.
IBM Cloud® Databases for MySQL allows you to horizontally scale your MySQL instance with Read Replicas in region or cross-regionally. Databases for MySQL Read Replicas can be easily transformed into fully functioning Databases for MySQL instances, an especially useful feature for online cross-regional disaster recovery strategies.

Additionally, Databases for MySQL provides independent scaling of disk, RAM, and vCPU, as well as auto-scaling capabilities and hourly billing. These features help provide greatly increase granularity on right-sizing database use for application workload.

Databases for MySQL is a multi-tenant offering by design and you have multiple levers for increased isolation that is detailed in our [Security and Compliance section](https://cloud.ibm.com/docs/cloud-databases?topic=cloud-databases-manage-security-compliance). For example, configuring a database with vCPUs (referred to as Dedicated Cores) introduces hypervisor-level isolation. Alternatively, if that particular lever of isolation is not necessary, you can configure databases so you pay solely for RAM and disk capacity. There are no restrictions on movement between these modes and it is an online activity to introduce or remove your usage of Dedicated Cores.





 Step 1: Before you begin 



* You need an [IBM Cloud account](https://cloud.ibm.com/registration).
* You need a Databases for MySQL deployment. Provision one from the [IBM Cloud catalog](https://cloud.ibm.com/catalog/services/databases-for-mysql). Give your deployment a memorable name that appears in your account's Resource List.
* Set the [Admin Password](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-admin-password) for your deployment.
* Install [MySQL Workbench](https://dev.mysql.com/downloads/workbench/).
The Dashboard Overview 

The Overview page shows you information about your IBM Cloud® Databases for Redis deployment. The overview includes essential identifying information.



 Overview 



 Type 

The type of database that is offered by the service, and the database version that your service uses.





 ID 

The ID is a [CRN (Cloud Resource Name)](https://cloud.ibm.com/docs/account?topic=account-crn) which uniquely identifies the database deployment. The CRN is used to refer to the database in the API and can be used with the CLI. Overview shows details of your service.





 Recent Tasks 

Every time that you make administrative changes to your service (such as scaling, or taking a manual backup), a task starts up. Recent Tasks shows the task name and progress bar for any running tasks, and a list of the most recent completed tasks. Depending on how busy your deployment is, successful tasks can be shown for 24-48 hours. Unsuccessful tasks can show for 7-8 days. Tasks can also be retrieved from the [Cloud Databases API](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-running-tasks-on-a-deployment) and [CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-tasks-list). A historical record of tasks from any time period is available through the [IBM Cloud® Activity Tracker integration](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-activity-tracker).





 Endpoints 

Endpoints within the Overview contains connection strings for your deployment. Each tab contains connection information that is tailored to the type of connection or the protocol that uses it. Basic information includes hostname, port, the TLS self-signed certificate, TLS/SSL parameters, and the default database of your deployment.
As root keys are encrypted by the master key that is owned by the user, no one else including IBM Cloud administrators can access your data.



Table 2. Supported database services

 Service Description Integration instruction 

 [IBM Cloud Databases for DataStax](https://cloud.ibm.com/docs/databases-for-cassandra) IBM Cloud Databases for DataStax is a scale-out NoSQL database service that is built on Apache Cassandra. It is designed to power real-time applications with high availability and massive scalability. [Hyper Protect Crypto Services integration](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-hpcs) 
 [IBM Cloud Databases for Elasticsearch](https://cloud.ibm.com/docs/databases-for-elasticsearch) IBM Cloud Databases for Elasticsearch is an enterprise-ready and fully managed Elasticsearch service that is built with native integration into IBM Cloud. [Hyper Protect Crypto Services integration](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-hpcs) 
 [IBM Cloud Databases for EnterpriseDB](https://cloud.ibm.com/docs/databases-for-enterprisedb) IBM Cloud Databases for EnterpriseDB is a database engine that optimizes the built-in features of PostgreSQL. You can gain greater scalability, security, and reliability along with enhancements that improve database administrator and developer productivity. [Hyper Protect Crypto Services integration](https://cloud.ibm.com/docs/databases-for-enterprisedb?topic=cloud-databases-hpcs) 
 [IBM Cloud Databases for etcd](https://cloud.ibm.com/docs/databases-for-etcd) IBM Cloud Databases for etcd is an enterprise-ready and fully managed etcd service that is built with native integration into the IBM Cloud. [Hyper Protect Crypto Services integration](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-hpcs)
The IBM Data Processing Addendum (Addendum) applies to the processing of client's personal data by IBM on behalf of client to provide IBM standard services.
[IBM DPA](https://www.ibm.com/support/customer/zz/en/dpa.html)

Databases for PostgreSQL processes limited client Personal Information (PI) in the course of running the service and optimizing the user experience.

Databases for PostgreSQL provides a [Data Sheet Addendum (DSA)](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=CD09D2E06DC811E8A0B560E89C071ECC) with its policies as a Data Processor regarding content and data protection.





 HIPAA 

Databases for PostgreSQL meets the required IBM controls that are commensurate with the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security and Privacy Rule requirements. These requirements include the appropriate administrative, physical, and technical safeguards required of Business Associates in 45 CFR Part 160 and Subparts A and C of Part 164. HIPAA must be requested at the time of provisioning and requires a representative to sign a Business Associate Addendum (BAA) agreement with IBM.





 PCI DSS 

Databases for PostgreSQL are compliant with the Payment Card Industry Data Security Standard (PCI DSS). IBM Cloud completes annual PCI DSS assessments by using an approved Qualified Security Assessor (QSA), and the resulting Attestations of Compliance (AOCs) and Service Responsibility Matrix (SRM) guides are available upon customer request. Auditors reviewed Databases for PostgreSQL for compliance under PCI DSS version 3.2.1 at Service Provider Level 1.

Customers are responsible for the storing, processing, and transmission of their cardholder data, and can create cardholder data environments (CDEs) that can store, transmit, or process cardholder data by using Databases for PostgreSQL. Customers can request and use the IBM Cloud AOCs and SRM guides when they seek their own PCI DSS certifications.
[83-Elements-of-the-cloud.svg](https://cloud.ibm.com/media/docs/images/homepage/83-Elements-of-the-cloud.svg)](https://www.ibm.com/training/cloud)[Community<br><br>Join the IBM Cloud community and collaborate with others.<br><br>![35-Connectivity.svg](https://cloud.ibm.com/media/docs/images/homepage/35-Connectivity.svg)](https://community.ibm.com/community/user/publiccloud/home)

 Latest updates 

[View more](https://cloud.ibm.com/docs/databases-for-mysql?topic=databases-for-mysql-mysql-relnotes)19 October 2022 | Deploying and Connecting an IBM Cloud® Databases Instance Tutorial

This tutorial guides you through the process of deploying a Cloud Databases instance and connecting it to a web front end by creating a webpage that allows visitors to input a word and its definition. These values are then stored in a database running on Cloud Databases. You install the database infrastructure by using Terraform and your web application uses the popular Express framework. The application can then be run locally, or by using Docker.

11 October 2022 | Protecting IBM Cloud® Databases for MySQL resources with context-based restrictions

Context-based restrictions (CBR) give account owners and administrators the ability to define and enforce access restrictions for IBM Cloud® resources based on the context of access requests. Access to Cloud Databases resources can be controlled with CBR and identity and access management (IAM) policies.

28 June 2022 | IBM Cloud® Databases for MySQL version 8 is now available on Cloud Databases

MySQL 8.0 is the latest version of the world's most popular open-source database. This release features improvements across the board, offering enhancements for better performance, reliability, security, and manageability, with significant improvements to the data dictionary.
The Dashboard Overview 

The Overview page shows you information about your IBM Cloud® Databases for etcd deployment. The overview includes essential identifying information.



 Overview 



 Type 

The type of database that is offered by the service, and the database version that your service uses.





 ID 

The ID is a [CRN (Cloud Resource Name)](https://cloud.ibm.com/docs/account?topic=account-crn) which uniquely identifies the database deployment. The CRN is used to refer to the database in the API and can be used with the CLI. The Overview pane shows details of your service.





 Recent Tasks 

Every time that you make administrative changes to your service (such as scaling, or taking a manual backup), a task starts up. The Recent Tasks panel shows the task name and progress bar for any running tasks, and a list of the most recently completed tasks. Depending on how busy your deployment is, successful tasks can be shown for 24 - 48 hours. Unsuccessful tasks can show for 7 - 8 days. Tasks can also be retrieved from the [Cloud Databases API](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-running-tasks-on-a-deployment) and [CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-tasks-list). A historical record of tasks from any time period is available through the [IBM Cloud® Activity Tracker integration](https://cloud.ibm.com/docs/databases-for-etcd?topic=cloud-databases-activity-tracker).





 Endpoints 

The Endpoints pane within the Overview pane contains connection strings for your deployment. Each tab contains connection information that is tailored to the type of connection or the protocol that uses it. Basic information includes things like hostname and port, as well as the TLS self-signed certificate, TLS/SSL parameters, and the default database of your deployment.
Monitoring Integration 

Monitoring for IBM Cloud® Databases for Elasticsearch deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward select information so you can monitor deployment health and resource usage. To see your Databases for Elasticsearch dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/6da1ae87b1f476791c38688e7a0b7f7c7a7d71b9/databases-for-elasticsearch/images/monitoring-ui-link.png)

Figure 1. Monitoring link

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/6da1ae87b1f476791c38688e7a0b7f7c7a7d71b9/databases-for-elasticsearch/images/monitoring-ibm-list.png)

Figure 2. Cloud databases dashboard



 Monitoring Availability 

IBM Cloud Monitoring is available for deployments in every region. Deployments in Multi-zone Regions (MZRs) - eu-gb, eu-de, us-east, us-south, jp-tok, au-syd - have their metrics in the corresponding region.
Monitoring Integration 

IBM Cloud® Databases for DataStax is deprecated and no longer supported as of 30 June 2024. For more information, see the [deprecation details](https://cloud.ibm.com/docs/databases-for-cassandra?topic=databases-for-cassandra-deprecationdep_details).

Monitoring for IBM Cloud® Databases for DataStax deployments is provided through integration with the IBM Cloud® Monitoring service. Your deployments forward selected information so you can monitor deployment health and resource usage. To see your Databases for DataStax dashboards in IBM Cloud Monitoring, you must [Enable Platform Metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-platform_metrics_enabling) in the same region as your deployment. If you have deployments in more than one region, you must provision IBM Cloud Monitoring and enable platform metrics in each region.

To access IBM Cloud Monitoring from your deployment, use the Monitoring link from the right menu. (If you do not already have a monitoring service in the same region as your deployment it says Add monitoring.)

The default dashboards are not shown until database instances begin emitting metrics.

Zoom

![The Monitoring link in a deployment](https://cloud.ibm.com/docs-content/v1/content/5b067197eff6fba69b2fcb2a802b03639f12f3d7/databases-for-cassandra/images/monitoring-ui-link.png)

Figure 1. The Monitoring link

To access your deployment's monitoring dashboard from IBM Cloud Monitoring, it's in the sidebar, under IBM.

Zoom

![Cloud databases dashboard in monitoring](https://cloud.ibm.com/docs-content/v1/content/5b067197eff6fba69b2fcb2a802b03639f12f3d7/databases-for-cassandra/images/monitoring-ibm-db-list.png)

Figure 2. Cloud databases dashboard



 Monitoring Availability 

IBM Cloud Monitoring is available for deployments in every region.
The Dashboard Overview 

The Overview page shows you information about your IBM Cloud® Databases for MongoDB deployment. The overview includes essential identifying information.



 Type 

The type of database that is offered by the service, and the database version that your service uses.





 ID 

The ID is a [CRN (Cloud Resource Name)](https://cloud.ibm.com/docs/account?topic=account-crn) which uniquely identifies the database deployment. The CRN is used to refer to the database in the API and can be used with the CLI.The Overview pane shows details of your service.





 Recent Tasks 

Every time that you make administrative changes to your service (such as scaling, or taking a manual backup), a task starts up. The Recent Tasks panel shows the task name and progress bar for any running tasks, and a list of the most recent completed tasks. Depending on how busy your deployment is, successful tasks can be shown for 24-48 hours. Unsuccessful tasks can show for 7-8 days. Tasks can also be retrieved from the [Cloud Databases API](https://cloud.ibm.com/apidocs/cloud-databases-apiget-currently-running-tasks-on-a-deployment) and [CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-tasks-list). A historical record of tasks from any time period is available through the [IBM Cloud® Activity Tracker integration](https://cloud.ibm.com/docs/databases-for-mongodb?topic=cloud-databases-activity-tracker).





 Endpoints 

The Endpoints pane within the Overview pane contains connection strings for your deployment. Each tab contains connection information tailored to the type of connection or the protocol that uses it. Basic information includes things like hostname and port, as well as the TLS self-signed certificate, TLS/SSL parameters, and the default database of your deployment.
* For larger databases of tens to hundreds of millions of documents or tens of GB, consider configuring your database to use 16 shards.
* For even larger databases, consider manually sharding your data into several databases. For such large databases, go to the [IBM Cloud Support portal](https://www.ibm.com/cloud/support) for advice.



The numbers in these guidelines are derived from observation and experience rather than precise calculation.





 Working with shards 



 Setting shard count 

The number of shards, Q, for a database is set when the database is created. The Q value cannot be changed later.

To specify the Q when you create a database, use the q query string parameter.

You can configure Q. However, you want to prohibit large values of Q since they have a deleterious effect on the service with no performance gain for the user.

If you attempt to set the Q value where it is not available, the result is a [403 response](https://cloud.ibm.com/apidocs/cloudantlist-of-http-codes) with a JSON body similar to the following example:

{
"error": "forbidden",
"reason": "q is not configurable"
}

It's possible to modify the configuration of a sharding topology for a database on dedicated database clusters. This modification can be done when the database is created. However, poor choices for configuration parameters can adversely affect database performance. For more information about modifying database configuration in a dedicated database environment, contact IBM Cloudant support.





 Setting the replica count 

In CouchDB version 2 onwards, you are allowed to [specify the replica count](https://docs.couchdb.org/en/stable/cluster/databases.htmlcreating-a-database) when you create a database. However, you are not allowed to change the replica count value from the default of 3. In particular, it is not possible to specify a different replica count value when you create a database. For further help, go to the [IBM Cloud Support portal](https://www.ibm.com/cloud/support).





 What are the R and W arguments?