vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Logging and monitoring 



 Journey Map 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/b7b9235ce6abd45b66931867c388cf107d38e15b/cloud-native-journey/kubernetes-on-vpc/images/logging/journey-map.png)

Set up logging and monitoring in IBM Cloud Kubernetes Service to help you troubleshoot issues and improve the health and performance of your Kubernetes clusters and apps.

Continuous monitoring and logging is the key to detecting attacks on your cluster and troubleshooting issues as they arise. By continuously monitoring your cluster, you're able to better understand your cluster capacity and the availability of resources that are available to your app. With this insight, you can prepare to protect your apps against downtime.





 Forward cluster and app logs to Log Analysis 

Use the IBM Cloud Kubernetes Service observability plug-in to create a logging configuration for Log Analysis in your cluster, and use this logging configuration to automatically collect and forward pod logs to IBM Cloud Log Analysis.

You can set up a logging configuration for your cluster from the console or CLI.



* [Forward logs to an IBM Cloud Log Analysis instance](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging)







 Forward cluster and app metrics to IBM Cloud Monitoring 

Use the IBM Cloud Kubernetes Service observability plug-in to create a monitoring configuration for IBM Cloud Monitoring in your cluster, and use this monitoring configuration to automatically collect and forward metrics to IBM Cloud Monitoring.

You can set up a monitoring configuration for your cluster from the console or CLI.



* [Forward metrics to an IBM Cloud Monitoring instance](https://cloud.ibm.com/docs/containers?topic=containers-health-monitormonitoring)







 Forward Kubernetes API audit logs to Log Analysis
* Why can't I migrate my virtual server?

You can migrate only private, dedicated hosts. For more information about migrating private, dedicated hosts, see [Migrating a dedicated host instance to another host](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-migrating-dedicated-host).
* What servers support suspend billing?

Your virtual server instance must be configured with the following settings to support the suspend billing feature.



* Hourly SAN
* A public profile from one of the following families



* Balanced
* Compute
* Memory
* Variable compute





* How do I change the operating system on my virtual server?

You can perform an OS reload to change the operating system on your virtual server at any time. For more information about OS reloads, see [Reloading the OS](https://cloud.ibm.com/docs/virtual-servers?topic=bare-metal-reloading-the-os).
* Why do web pages load slowly on Linux?

Slow loading web pages can be caused by several issues.



* Over-utilization of server resources. Check your monitoring tools to find any potential bottlenecks in server resources.
* Configuration file limits with Apache, PHP, or SQL. For more information, see [Apache configuration files](https://httpd.apache.org/docs/2.4/configuring.html).
* Network latency or packet loss.



* DoS attack might be targeting services or oversaturating the network.





For more information about troubleshooting Linux network speed issues, see [Using iPerf to Troubleshoot Speed and Throughput Issues](https://www.ibm.com/cloud/blog/using-iperf-to-troubleshoot-speed-and-throughput-issues?mhsrc=ibmsearch_a&mhq=iperf).
* Why do I have RHEL package issues?

If you experience one of the following RHEL package issues, see the possible solutions.



* Can't download new packages for RHEL servers
* Can't update packages through YUM
curl https://private.directlink.cloud.ibm.com/v1/direct_links?version='2020-03-31' -H "Authorization: Bearer $iam_token"





 Using the VPE with the SDK 

After creating an endpoint gateway for Direct Link, you must use the private endpoint's FQDN when setting the service's FQDN during construction of the direct link service object.

private.directlink.cloud.ibm.com

For examples of setting the service's FQDN for the specific SDK language, see [SDK API examples](https://cloud.ibm.com/apidocs/direct_link?code=goauthentication).





 Using the VPE with Terraform 

If you plan to access the Direct Link service using Terraform, make sure to set the IBMCLOUD_DL_API_ENDPOINT environment variable to private.directlink.cloud.ibm.com. For example:

export IBMCLOUD_DL_API_ENDPOINT=private.directlink.cloud.ibm.com

For more information, see [Direct Link resources and data sources](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-resources-datasource-listibm-directlink-gateway_rd).
* Solution: When you use the Analyze API to apply a Watson Knowledge Studio model enrichment to a collection, keep the size of the input document under 50 KB.







 2.2.1 issues that were fixed in subsequent releases 



* [Fixed in version 4] If you add an IBM Watson® Knowledge Studio machine learning enrichment to a collection, the ingestion process might run very slowly but will eventually complete. If ingestion processes slowly, you might see the following error message in Warnings and errors:

[WKSML_MODEL_NAME]: Document analysis timed out

For additional timeout details, you can check your Knowledge Studio machine learning logs, which might look similar to the following:

{
"message": "Analysis failed due to:
org.apache.uima.analysis_engine.AnalysisEngineProcessException
at c.i.n.b.SIREAnnotator.process(_:454)
... ",
"level": "SEVERE",
}

Documents that time out during processing are indexed without Knowledge Studio enrichment results.









 2.2.1, 26 February 2021 



* Deployment timing issue:



* Error: After installing patch 7, when you try to provision a service instance, a 404 Not Found error is displayed. The following message might be logged for the nginx pods: open() "/usr/local/openresty/nginx/html/watson/common/discovery/auth" failed (2: No such file or directory)
* Solution: Restart the zen-watcher pod.



* If you perform an air-gapped installation that pulls container images from an external container registry, you might experience the following issue:



* Error: Some Discovery pods might report an ImagePullBackoff error.
* Cause: The wrong image pull secret is being used.
* Solution: Complete the following steps during the installation:



* Start installing Watson Discovery.
* After watson-discovery-operator module completes, check if a WatsonDiscovery custom resource is created by running the following command:

oc get WatsonDiscovery wd
* After the custom resource is created, run the following commands to point the correct image pull secret to pull images from the external registry:
* Remove support for .NET Core SDK 2.0.0-preview2-006497
* Remove support for .NET Framework 1.0.4
* Remove support for .NET Framework 1.1.1
* Update Node.js version to 6.14.3
* Change default .NET Core SDK 2.1.301







 7 September 2018 

Updated Node.js buildpack v3.22
: Beginning with this buildpack, the SDK for Node.js buildpack includes the Node.js community release runtimes for version 6.x and 8.x. With this change, the Node.js OpenSSL FIPS module is no longer included in these versions of the buildpack. Only version 4.x continues to include the OpenSSL FIPS module.

The SDK for Node.js buildpack v3.22 provides IBM SDK for Node.js versions 4.8.5, 4.8.7 and Node.js community versions 6.14.3, 6.14.4, 8.11.3 and 8.11.4. The default is latest 6.x, so it is currently 6.14.4.

This release also includes fixes for the following security vulnerability:



* [CVE-2018-0732](https://www.ibm.com/support/pages/node/715089)







 10 August 2018 

Updated Liberty buildpack v3.24-20180806-1313
: The monthly Liberty runtime version was updated to 2018.8.0.0.



* The IBM JRE version was updated to 8 SR5 FP17.







 24 July 2018 

Updated Node.js buildpack v3.21
: Beginning with the latest Node.js 6.x and 8.x versions in this release, the SDK for Node.js buildpack is based on the Node.js community release. With this change, the Node.js OpenSSL FIPS module in the buildpack will no longer be updated. The current OpenSSL FIPS module and IBM SDK for Node.js builds are eligible for removal as of 24 August 2018.
Logging and monitoring 



 Journey Map 

![Architecture](https://cloud.ibm.com/docs-content/v1/content/b7b9235ce6abd45b66931867c388cf107d38e15b/cloud-native-journey/roks-on-vpc/images/logging/journey-map.png)

Set up logging and monitoring in Red Hat® OpenShift® on IBM Cloud® to help you troubleshoot issues and improve the health and performance of your Kubernetes clusters and apps.

Continuous monitoring and logging is the key to detecting attacks on your cluster and troubleshooting issues as they arise. By continuously monitoring your cluster, you're able to better understand your cluster capacity and the availability of resources that are available to your app. With this insight, you can prepare to protect your apps against downtime.





 Forward cluster and app logs to Log Analysis 

Use the Red Hat® OpenShift® on IBM Cloud® observability plug-in to create a logging configuration for Log Analysis in your cluster, and use this logging configuration to automatically collect and forward pod logs to IBM Cloud Log Analysis.

You can set up a logging configuration for your cluster from the console or CLI.



* [Forward logs to an IBM Cloud Log Analysis instance](https://cloud.ibm.com/docs/openshift?topic=openshift-healthopenshift_logging)
* [Using the cluster logging operator](https://cloud.ibm.com/docs/openshift?topic=openshift-healthoc_logging_operator)







 Forward cluster and app metrics to IBM Cloud Monitoring 

Use the Red Hat® OpenShift® on IBM Cloud® observability plug-in to create a monitoring configuration for IBM Cloud Monitoring in your cluster, and use this monitoring configuration to automatically collect and forward metrics to IBM Cloud Monitoring.

You can set up a monitoring configuration for your cluster from the console or CLI.



* [Forward cluster and app metrics to an IBM Cloud Monitoring instance](https://cloud.ibm.com/docs/openshift?topic=openshift-health-monitoropenshift_monitoring)
: You can now create pre-MFA extensions that allow you to make custom decisions at runtime about which users must complete your MFA flow. For more information, see the [extending MFA docs](https://cloud.ibm.com/docs/appid?topic=appid-cd-mfacd-mfa-extensions).





 15 December 2019 

Access control
: You can now define which users are able to access your app data, use specific features, or perform specific actions in your apps by using role-based access control. For more information, see the [access control docs](https://cloud.ibm.com/docs/appid?topic=appid-access-control).

Cloud Directory: Custom MFA flows
: You can now make custom decisions about who must complete the MFA flow by configuring your own extension and registering it with App ID. For more information, see [Customizing MFA](https://cloud.ibm.com/docs/appid?topic=appid-cd-mfacd-premfa).





 22 November 2019 

Single-page applications: SDK
: Don't manage a backend for your app? You can now easily secure your browser applications by using the JavaScript SDK. For more information, see the [SPA docs](https://cloud.ibm.com/docs/appid?topic=appid-single-page).





 12 September 2019 

Increase the security of your SAML flow
: You can now increase the security of your SAML work flows by enabling request signing and response encryption. For more information, see [SAML](https://cloud.ibm.com/docs/appid?topic=appid-enterprise).





 8 August 2019 

Track runtime authentication events with Activity Tracker
: Now you can track, manage, and analyze authentication events that are performed by your app users at runtime by [integrating Activity Tracker and App ID](https://cloud.ibm.com/docs/appid?topic=appid-at-eventsat-monitor-runtime). Releasing your secured custom, mobile, or web app to your users is only the beginning of your journey toward adoption.
: Note that the pod and service subnets can't overlap. The pod subnet is in the 172.30.0.0/16 range by default.

--skip-advance-permissions-check
: Optional: Skip [the check for infrastructure permissions](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-cliinfra_permissions_get) before creating the cluster. Note that if you don't have the correct infrastructure permissions, the cluster creation might only partially succeed, such as the master provisioning but the worker nodes unable to provision. You might skip the permissions check if you want to continue an otherwise blocked operation, such as when you use multiple infrastructure accounts and can handle the infrastructure resources separately from the master, if needed later.

--entitlement cloud_pak
: Include this option only if you use this cluster with an [IBM Cloud Pak](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_cloud_paks) that has a Red Hat OpenShift entitlement. When you specify the number of workers (--workers) and flavor (--flavor), make sure to specify only the number and size of worker nodes that you are entitled to use in [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/index.html). After your cluster is created, you are not charged the Red Hat OpenShift license fee for the entitled worker nodes in the default worker pool. Do not exceed your entitlement. Keep in mind that your OpenShift Container Platform entitlements can be used with other cloud providers or in other environments. To avoid billing issues later, make sure that you use only what you are entitled to use. For example, you might have an entitlement for the OCP licenses for two worker nodes of 4 CPU and 16 GB memory, and you create this worker pool with two worker nodes of 4 CPU and 16 GB memory. You used your entire entitlement, and you can't use the same entitlement for other worker pools, cloud providers, or environments.

-q
Examples Some of the unrecognized requests are shown as a preview. 
 Request count The number of unrecognized requests in the group. Focus on groups with a higher count of unrecognized requests. 
 Percentage The percentage of unrecognized requests relative to the other groups. Focus on groups with a higher percentage of unrecognized requests. 







 Creating actions from unrecognized requests 

To create actions based on unrecognized requests:



1. Click a group to open its page. Each unrecognized request is listed individually.



Unrecognized request group page

 Column Description 

 Unrecognized requests Verbatim requests from customer conversations 
 Request count The number of times the unrecognized request is included in this group 
 Related actions Existing actions that you might modify to address the unrecognized request 



2. If Watson Assistant identifies more similarities among the examples, you can click Grouped by similarity to further categorize the list.

Zoom

![Grouped by similarity](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/analytics-unrecognized-grouped-by-similarity.png)

Grouped by similarity

In a group named expense reimbursement application, requests might be further grouped by similarity. For example:



* Problems logging in to or starting the expense reimbursement application
* Issues with crashes of the expense reimbursement application
* Requests for help or assistance with the expense reimbursement application



These similarities can help you decide to add one or more actions that correspond to what you want to cover with your assistant, rather than adding all requests to a single action.
3. You can click to select unrecognized requests that you want to use as example phrases in a new action.

Zoom

!
Version 1.1.3 is available
: Text to Speech for IBM Cloud Pak for Data version 1.1.3 is now available.





 27 November 2019 (Version 1.1.2) 

Version 1.1.2 is available
: Text to Speech for IBM Cloud Pak for Data version 1.1.2 is now available.





 30 August 2019 (Version 1.0.1) 

Version 1.0.1 is available
: Text to Speech for IBM Cloud Pak for Data version 1.0.1 is now available. The service now works with IBM Cloud Pak for Data 2.1.0.1. The service now supports installing IBM Cloud Pak for Data with Red Hat OpenShift.

New Japanese neural voice
: The service now offers the neural Japanese voice ja-JP_EmiV3Voice. For more information, see [Supported languages and voices](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-voiceslanguage-voices).

FISMA support
: Federal Information Security Management Act (FISMA) support is now available for Text to Speech for IBM Cloud Pak for Data. The service is FISMA High Ready.





 28 June 2019 (Version 1.0.0) 

Version 1.0.0 is available
: Version 1.0.0, the initial release of the service, is now available. Text to Speech for IBM Cloud Pak for Data is based on the IBM Watson® Text to Speech service on the public IBM Cloud. Text to Speech for IBM Cloud Pak for Data differs from the public Text to Speech service in the following ways. You might find this information helpful if you are already familiar with the Text to Speech service on the public IBM Cloud.



* Text to Speech for IBM Cloud Pak for Data uses access tokens for authentication. For more information, see the [API & SDK reference](https://cloud.ibm.com/apidocs/text-to-speech).
* The endpoints for Text to Speech for IBM Cloud Pak for Data are specific to your IBM Cloud Pak for Data cluster.
When you delete a file share, those blocks must be overwritten before that file storage is made available again, either to you or to another customer.

Further, when IBM decommissions a physical drive, the drive is destroyed before their disposal. Decommissioned physical drives are unusable and any data on them is inaccessible.





 File share lifecycle states 

Table 1 describes the states in the file share lifecycle.



Table 1. File storage lifecycle states

 Status Explanation 

 Stable The file share or mount target is stable and available for use. 
 Pending The file share or mount target is being created. 
 Failed The file share or mount target failed to be created. You can delete the failed share and try creating another one. 
 Deleting The file share or mount target is being deleted. 
 Deleted The file share or mount target is deleted. 
 Initializing The file share replica is being created. 
 Split_pending The replica file share is being split from the source share. 
 Failover_pending The source file share is failing over to the replica file share, which becomes read/write and the new source share. 







 Managing security and compliance 

File Storage for VPC is integrated with the Security and Compliance Center to help you manage security and compliance for your organization. You can set up goals that check whether file shares are encrypted by using customer-managed keys. By using the Security and Compliance Center to validate the file service configurations in your account against a profile, you can identify potential issues as they arise.

For more information, see [Monitoring security and compliance posture with VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-security-compliancemonitor-vpc). For more information about creating security and compliance goals, see [Defining rules](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-rules-define&interface=ui) in the Security and Compliance documentation.





 Limitations in this release 

The following limitations apply to this release of File Storage for VPC.



* File share size cannot be increased after it is created.
* Previous profiles are not supported when you provision a new file share, which is based on the dp2 profile.
You can use [web app strategy](https://cloud.ibm.com/docs/appid?topic=appid-key-conceptsterm-web-strategy) to check whether a request contains any scopes by using the hasScope method. When a user with an assigned role signs in, they are granted access by an App ID token that contains all the scopes that are defined in the role. For example, if you're working with the Node.js SDK, your code snippet would look similar to the following:

app.get("/protected", passport.authenticate(WebAppStrategy.STRATEGY_NAME), function(req, res){
    if(WebAppStrategy.hasScope(req, "read write")){
              res.json(req.user);
    }
    else {
        res.send("insufficient scopes");
    }
});





 When using API strategy 

You can define the scopes that are required to access a specific endpoint by adding a scope variable to your [API strategy](https://cloud.ibm.com/docs/appid?topic=appid-key-conceptsterm-api-strategy) code. For instance, if you have an application that is written in Node.js and you're working with the Node.js SDK, your code snippet might look similar to the following.

app.get("/api/protected",
        passport.authenticate(APIStrategy.STRATEGY_NAME, {
                audience: "myApp",
                scope: "read write update"
        }),
        function(req, res) {
                res.send("Hello from protected resource");
        }
);



Table 3. Understanding the variables used with API strategy

 Variable Description 

 scope The required scopes, which are separated by a space. 
 audience The application client ID. 









 Removing access 

You can delete any scope or role that's no longer needed.



 Deleting scopes with the UI 

If you no longer need a scope, you can delete it by using the App ID UI.
ABAP SDK for IBM Watson 

The ABAP SDK for IBM Watson, enables developers to easily call and use IBM Watson Developer Services directly from ABAP to create an Intelligent Enterprise.

ABAP SDK is a community-driven SDK for the ABAP open source community that is written by ABAPers from IBM Cloud, IBM Services, and IBM Systems. The SDK includes tight collaboration with the SAP Cloud Platform ABAP Environment development team to provide optimal usage of IBM Watson for side-by-side extensibility development.

The ABAP SDK includes over 40,000 lines of ABAP code so that any ABAP developer needs to use only 10 - 20 lines of ABAP code to call IBM Watson APIs.



 Summary of ABAP SDK capabilities 

The ABAP SDK for IBM Watson includes:



* Pre-built Classes for each IBM Watson API; use only 10 - 20 lines to call IBM Watson APIs
* Pre-built Methods and data types
* API responses that are provided in ABAP Structures or Tables
* Packaged using [abapGit (Git client for ABAP)](https://docs.abapgit.org), for easy use with [APACK (package and dependency manager)](https://docs.abapgit.org/ref-apack.html)
* SAP-standard-generated documentation (abap-docs)



This IBM first-of-a-kind release of ABAP code to open source (licensed under the [Apache 2.0 license](http://www.apache.org/licenses/LICENSE-2.0)), is designed for and released with variants for both:



* SAP NetWeaver Application Server 7.50+
* SAP Cloud Platform ABAP Environment 2002+



The ABAP SDK for IBM Watson is available in two variants:



* [ABAP SDK for IBM Watson, using SAP NetWeaver](https://github.com/watson-developer-cloud/abap-sdk-nwas)
* [ABAP SDK for IBM Watson, using SAP Cloud Platform ABAP Environment](https://github.com/watson-developer-cloud/abap-sdk-scp)



It is tested with: