vania-janet/multiturn-rag-retrieval-data huggingface dataset:
streaming_statistics JSON object Contains information and statistics related to the Text to Speech synthesis and playback. 



The response.streaming_statistics object contains the following keys:



Keys for the response.streaming_statistics object

 Key Type Description 

 transaction_id string A unique identifier of the transaction. 
 start_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the transaction started. 
 stop_timestamp string. Time in the ISO format yyyy-MM-ddTHH:mm:ss.SSSZ Time when the transaction ended. 
 response_milliseconds number Time in milliseconds between when a text utterance is sent to the Text to Speech service and when the phone integration receives the first packet of synthesized audio. 



The max_response_milliseconds object contains the following keys:



Keys for the max_response_milliseconds object

 Key Type Description 

 assistant number Maximum round-trip latency in milliseconds, calculated from all Watson Assistant requests related to the call. 
 text_to_speech number Maximum time in milliseconds between when a text utterance is sent to the Text to Speech service and when the phone integration receives the first packet of synthesized audio. Calculated from all the Text to Speech requests related to this call. 
 speech_to_text number Maximum latency in milliseconds between when silence is detected in the user's speech and a final result from Speech to Text is received. This value is calculated from all the Speech to Text recognition results related to this call. 





 Mapping between CDR and Watson Assistant response types 



Mapping between CDR and Watson Assistant response types

 CDR response type Watson Assistant response type 

 text_to_speech text 
 url audio 
 dtmf dtmf, command_info.type : send 
 sms user_defined, vgwAction.command : vgwActSendSMS 
 transfer connect_to_agent 
 text_to_speech_config text_to_speech, command_info.type : configure 
 speech_to_text_config speech_to_text, command_info.type : configure
Methods for verification include email, text, or phone call, and you can use any combination of those options to verify your identity. After you verify your identity, you set up your authentication factors. If you need to update your verification methods or authentication factors later, see [Managing verification methods and MFA factors](https://cloud.ibm.com/docs/account?topic=account-verification-authentication).



 Enabling MFA for an account 



1. In the IBM Cloud console, go to Manage > Access (IAM) > Settings.
2. Click Authentication.
3. Select the type of MFA that you want to enable in your account. For more information about the MFA options, see [ID-based MFA options](https://cloud.ibm.com/docs/account?topic=account-typesid-based).







 Enabling MFA for an individual user 



1. In the IBM Cloud console, go to Manage > Access (IAM) > Users and select the user whose MFA you want to update.
2. Go to the MFA section and click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg).
3. Select the type of MFA to enable for the user.

By default, Use account default is selected. The account default is the MFA option that is enabled at the account level. To view the account default, go to Manage > Access (IAM) > Settings > Authentication.
4. Click Save.



You can view a list of users in your account that have an MFA requirement that is different from the account's default by going to Manage > Access (IAM) > Settings > Authentication. Then, view the User-specific MFA section.







 Disabling MFA 

Disabling MFA does not affect users that are already logged in. The action impacts all new logins.



 Disabling MFA for an account 



1.
Command options 



* --all or -a Display instance name and CRN.
* --json or -j Display results as JSON.







 Examples 

List all current deployments with an account.

ibmcloud cdb ls







 ibmcloud cdb deployment-about 

Short version - about

Use this command to get details of which database is deployed within the instance, which version, and any options applied. Also displayed are the ID and GUID for the resource controller, resource plans, current state, type, and last known operation.

ibmcloud cdb deployment-about <deployment name or CRN> [--all] [--json]



 Command options 



* --all or -a Display all the available data from the resource controller's records.
* --json or -j Display results as JSON.







 Examples 

List details of a deployment named "RedisDBOne".

ibmcloud cdb about RedisDBOne









 Connections 

Get connection strings and certificate information to use when you connect to your deployment. Manage connections for those databases that have the option.



 ibmcloud cdb deployment-connections 

Short version - cxn

Displays connection strings and other connection details for a deployment with or without user credentials inserted.

ibmcloud cdb deployment-connections [--user <userid>] [--password <password>] [--endpoint-type <endpoint type>] [--all] [--only] [--start] [--certroot <path>] [--json]



 Command options 



* --start or -s Start a connection by running the CLI command generated. If a password isn't specified in the flags, the command prompts for a password interactively. The plug-in uses the default commands for command-line interaction and managing the CA certificate to ensure a secure TLS session. Defaults to connecting as the deployment's admin user.
* --user <userid> or -u Sets the user ID that is used when retrieving connection settings. It is substituted into connection strings. Defaults to the deployment's admin user.
Connecting with etcdctl 

You can access your etcd database directly from a command-line client, which allows for direct interaction with the data structures that are created within the database. It is also useful for administering and monitoring the keyspace and performance, making etcd transactions, managing leases, and other management activities.

Databases for etcd only supports the etcd v3 API and datastore. Access to the v2 API is disabled.



 Installing 

The etcdctl binary is available in the etcd distribution, which can be downloaded from [the coreos/etcd repository](https://github.com/coreos/etcd/releases/latest).





 Connecting 

Connection strings are displayed in the Endpoints panel of your deployment's Overview, and can also be retrieved from the [cloud databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-connections), and the [API](https://cloud.ibm.com/apidocs/cloud-databases-apidiscover-connection-information-for-a-deployment-f-e81026).

Zoom

![CLI Endpoints page](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/images/cli-endpoints-pane.png)

Figure 1. CLI Endpoints page

Any user on your deployment is able to connect by using etcdctl, but the [root user](https://cloud.ibm.com/docs/databases-for-etcd?topic=databases-for-etcd-user-managementthe-root-user) does have more permissions on the cluster.
Updating your profile 

In your IBM Cloud® profile, you can add a photo and personal information, manage notifications, and monitor your privacy. Setting it up helps your teammates know who you are and how you can help.

Your profile is connected to your log in ID, and it's shared across all IBM Cloud accounts that you can access.



 Changing your profile photo 

You can change your profile photo. In the IBM Cloud console, to the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Profile.



* To add a photo or replace an existing photo, click Upload.
* To remove your photo, click Delete picture.



The maximum file size for a profile picture is 100 KB. Use only PNG or JPG files.





 Editing your information 

If you log in with an IBMid, it is the single ID that you use to log in to your IBM Cloud account for infrastructure, services, and application features. You can't change your IBMid, but you can edit your associated profile information, such as your name, email, phone number, password, or company name. In the console, go to the Avatar icon ![Avatar icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/i-avatar-icon.svg) > Profile. If you log in with a SoftLayer ID, you can also change your profile information from the Profile page.

If you log in with an ID from an external identity provider (IdP), then your information from your IdP is displayed. However, you can't update it on the Profile page. You must update your user information with your IdP.





 Changing your cookie settings 

The IBM Cloud console requires cookies to manage your sessions, such as to provide secure login, handle transactions, and save some preferences.
* UI
* API







 Auditing system events for classic infrastructure 

If you have a classic infrastructure account, you can monitor storage replication events by viewing audit logs. Audit logs track the interactions of each user, like login attempts, port speed updates, power restarts, and interactions made by IBM Cloud infrastructure support staff.



 Viewing your audit log in the console 

To view your audit log, go to Manage > Account in the IBM Cloud® console, and select Audit log. The audit log initially displays the last 25 interactions that were taken by users on the account. You can view up to 200 interactions at any time. Expand the items per page menu to see more results.



 Viewing a user's access logs 

From the audit log page, you can also see data for each access attempt that is made by a specific user. The logs display a date and timestamp and IP address for each access attempt. Use the following steps to view a user's Access Logs.



1. Go to Manage > Account in the IBM Cloud console, and select Audit log.
2. Then, filter for the user, select the timeframe that you want to view, and choose an object type.



The access log for each user displays the access attempts that were made by that user by date, along with the IP address from which the access attempt was made. Information within the access log is read-only.





 Granting access to the audit log 

The Viewer role or higher on all account management services is required to view the audit log. For classic infrastructure permissions, a user must be assigned the Super user role.







 Viewing your audit log by using the SoftLayer API 

You can use the SoftLayer API to view your audit log. The SoftLayer® Application Programming Interface is the development interface that gives developers and system administrators direct interaction with IBM Cloud backend system. The SoftLayer API powers many of the features in the IBM Cloud console, which typically means if an interaction is possible in the IBM Cloud console, it can also be run in the API. Because you can programmatically interact with all portions of the IBM Cloud environment within the API, you can automate tasks with SoftLayer API.

The SoftLayer API is a Remote Procedure Call system.
You can call this method on any object or field. If the conversion fails, null is returned.





 toInt() 

Converts the object or field to the Integer number type. You can call this method on any object or field. If the conversion fails, null is returned.





 toLong() 

Converts the object or field to the Long number type. You can call this method on any object or field. If the conversion fails, null is returned.

If you specify a Long number type in a SpEL expression, you must append an L to the number to identify it as such. For example, 5000000000L. This syntax is required for any numbers that do not fit into the 32-bit Integer type. For example, numbers that are greater than 2^31 (2,147,483,648) or lower than -2^31 (-2,147,483,648) are considered Long number types. Long number types have a minimum value of -2^63 and a maximum value of 2^63-1 (or 9,223,372,036,854,775,807).

If you need to find out if a number is too long to be recognized properly in the dialog, you can check whether there are more than 18 integers in the number by using an expression like this:

 {: codeblock}

18 ?>

If you need to work with numbers that are longer than 18 integers, consider using a pattern entity (with a regular expression such as d{20}) to work with them instead of using @sys-number.

 Standard math {: dialog-methods-numbers-standard-math}

Use SpEL expressions to define standard math equations, where the operators are represented by using these symbols:

 Arithmetic operation Symbol 

 addition + 
 division / 
 multiplication * 
 subraction 

For example, in a dialog node response, you might add a context variable that captures a number specified in the user input (@sys-number), and saves it as $your_number. You can then add the following text as a text response:

 {: codeblock}
I'm doing math.
An integer number is represented by a sequence of at least one digit, thus 0 to 9. The integer number can have a suffix denoting the type of integer number. The three types of integer numbers are:



* Y: tiny integer number
* S: small integer number
* L: large integer number



For more information about data types, see [dataType](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencedataType).





 Decimal number 

The following is a decimal number:



* A sequence of at least one digit followed by a positive or negative exponent, for example, 10E2 represents integer 1000 and 1E-1 represents 0.1.
* A decimal number, for example, 3.14.
* A decimal number followed by a positive or negative exponent, for example, 3.14E+3 represents 3140.00 or 3.14E-3 represents 0.00314.



The decimal number can have a suffix denoting the type of decimal number. The two types of decimal numbers are:



* D: double decimal number
* BD: large decimal number



For more information about data types, see [dataType](https://cloud.ibm.com/docs/sql-query?topic=sql-query-sql-referencedataType).







 String 

A string is a sequence of arbitrary characters that includes escaped characters, for example, t, either enclosed in single quotation marks ', or double quotation marks ". To include any quotation mark characters in the string, they must be escaped as \' or \".
Debugging subscriptions 

Use the tips to learn how to troubleshoot IBM Cloud® Code Engine subscriptions.



  Subscription limits to consider 

The maximum number of IBM Cloud Object Storage subscriptions that you can have per project is 100. You are limited to a total of 100 cron subscriptions per project.

For more information about limits for subscriptions, see [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).





  Subscription logs 

You can retrieve the logs of the Object Storage subscription for further debugging by using [IBM Log Analysis](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-mm-cos-integration) for log management capabilities.
DNS Services allows creating a private DNS zone that can have the same name as the public DNS zone. See a [detailed explanation](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-about-dns-servicesresolving-dns-names-with-dns-services) of this scenario, referred to as Split Horizon.
* Are there any limits on global load balancer usage?

See [Global load balancers limitations](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-global-load-balancersglb-ki) for more information on global load balancer usage.
* What types of health checks are supported?

HTTP and HTTPS health checks are currently supported.
* What regions can I use for health check monitoring?

Health checks are currently supported in the following regions:



* Dallas (us-south)
* Washington, D.C. (us-east)
* London (eu-gb)
* Frankfurt (eu-de)
* Osaka (jp-osa)
* Tokyo (jp-tok)
* Toronto (ca-tor)
* Sydney (au-syd)
* Sao Paulo (br-sao)



* How can I disable health check monitoring to the origins?

You can disable health check monitoring by disabling the origin.
* How do I upgrade my plan from free to standard?



1. Navigate to the Resource List in the [IBM Cloud console](https://%7BDomainName%7D/).
2. Select the instance of DNS Services you want to upgrade.
3. Select Plan from the navigation menu.
4. Select Standard DNS from the plan table.
5. Click Save and then click OK when prompted to verify 'Are you sure that you want to change plans?'.
replica = 3. Note when the number of replica is changed, then the JR_MAXJOBS settings must also be updated. 



You can customize by following the steps to [edit the default configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-configure-k8s-clusteredit-agent-namespace-confg).





 Agent job-runner configuration 

The following resource limits and replicas are the default configuration applied to the schematics-job-runner namespace



Default agent job-runner

 Parameter Description 

 resource-limits Resource limit setting for the jobrunner are cpu = 500m, and memory = 1Gi. 
 replicas Number of job pods. replica = 1. Note when the number of replica is changed, then the JR_MAXJOBS settings must also be updated. 



You can customize the job-runner configuration following the steps, [editing the default configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-configure-k8s-clusteredit-agent-namespace-confg).





 Sandbox configuration 

Following resource limits and replicas are the default configuration applied to the schematics-sandbox namespace.



Sandbox deployments

 Parameter Description 

 resource-limits Resource limit setting for the sandbox are cpu = 500m, and memory = 1Gi. 
 replicas Number of job pods. replica = 3. Note when the number of replica is changed, then the JR_MAXJOBS settings must also be updated. 



You can customize the sandbox configuring following the steps, [editing the default configuration](https://cloud.ibm.com/docs/schematics?topic=schematics-configure-k8s-clusteredit-agent-namespace-confg).





 Schematics agents controller manager 

The following resource limits and replicas are the default configuration applied in the schematics-agents-observe namespace.



Schematics agent controller manager deployments

 Parameter Description
I'm over my limit for jobs or job runs. How can I delete them? 

 What’s happening 

You receive a message that the limit for jobs or job runs is exceeded.

 Why it’s happening 

Code Engine has quotas for jobs and job runs within a project.

You are limited to 100 jobs per project and 100 job runs per project before you need to clean up old ones. See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).

Use one of the following ways to check that the quota limit for jobs and job runs is not exceeded.



* From the console, select your project and then go to the Code Engine Overview page. You can view the number of jobs and job runs for the project in the Summary section. For more details, select Jobs or Job runs from the Summary section or select Jobs from the navigation menu.
* With the CLI,



* Run the [ibmcloud ce jobrun list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-list) command to list all your defined job runs.
* Run the [ibmcloud ce job list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-list) command to list all your defined jobs.





 How to fix it 

If the number of jobs or job runs is near the quota limit, delete job runs and then jobs as needed.

When you delete a job, all the submitted job runs that reference this job are also deleted.



* From the console, select your project and then go to the Code Engine Overview page. You can view the number of jobs and job runs for the project in the Summary section. For more details, select Jobs or Job runs from the Summary section or select Jobs from the navigation menu.



* To delete a specific job run of a job, select the job from the Jobs page. From the specific job page, click the name of the job run from the Latest job runs section, and then select Delete job run in the drop-down menu.
As a consequence of the end of FAQ extraction support, the COVID-19 kit data collection will stop being supported also.

Known issue for training. You might encounter the following issue when you try to train your data collection:



* Error: If you are training your collection, you might see the message, Your query can not be run because you have exceeded the rate limit for your plan. Your current plan limits the number of complex queries you can run simultaneously, so you can fix this by upgrading or reducing the number of queries.
* Cause: If you have a very small plan (XS or S), you might encounter this problem because your plan limits the number of queries that you can submit at one time. This message might be displayed even when you aren't submitting test queries because the product user interface can send some queries in the background to update the training page.
* Solution: Close the training page or view a different page and then try to submit your query again. As a longer term fix, consider upgrading your plan.







 11 January 2022 

Operation limits : New limits were applied to long-running operations, such as ingestion. For more information, see [Troubleshooting ingestion issues](https://cloud.ibm.com/docs/discovery?topic=discovery-addcontentadding-ts).





 8 October 2021 

Deprecated Discovery News : The Watson Discovery News feature is deprecated as of 8 October 2021. Existing News collections are available and support continues until 8 October 2022, after which date they will no longer be accessible. The Discovery News collection is not available in Watson Discovery v2 service instances.





 22 September 2020 

New beta FAQ extraction : Released the beta version of [FAQ extraction](https://cloud.ibm.com/docs/discovery?topic=discovery-sourcesconnectwebcrawl). This beta feature is only available if you build a search skill in Watson Assistant and configure a web crawl. FAQ extraction automatically extracts question-and-answer pairs from your FAQ web pages so that Watson Assistant returns more precise answers.





 12 August 2020 

Deprecated anomaly detection : Anomaly detection is deprecated and no longer available, effective 12 September 2020.
Managing IBM Cloud® Databases for PostgreSQL Connections 

Connections to your IBM Cloud® Databases for PostgreSQL deployment use resources, so it is important to consider how many connections you need when tuning your deployment's performance. PostgreSQL uses a max_connections setting to limit the number of connections (and resources that are consumed by connections) to prevent run-away connection behavior from overwhelming your deployment's resources.

You can check the value of max_connections with your [admin user](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-user-managementthe-admin-user) and [psql](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-connecting-psql).

ibmclouddb=> SHOW max_connections;
max_connections
-----------------
115
(1 row)

Many of the queries rely on the admin user's role as pg_monitor, which is only available in PostgreSQL 10 and newer. Users on PostgreSQL 9.x, might not have permissions to run all of the queries in these docs.



 PostgreSQL Connection Limits 

At provision, Databases for PostgreSQL sets the maximum number of connections to your PostgreSQL database to 115. 15 connections are reserved for the superuser to maintain the state and integrity of your database, and 100 connections are available for you and your applications. If the number of connections to the database exceeds the 100-connection limit, new connections fail and return an error.

FATAL: remaining connection slots are reserved for
non-replication superuser connections

Exceeding the connection limit for your deployment can cause your database to be unreachable by your applications.

You can check the number of connections to your deployment with the admin user, psql, and pg_stat_database.

SELECT count(distinct(numbackends)) FROM pg_stat_database;