vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Logging with Cloud Foundry 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

In IBM Cloud® public, you can monitor logs from Cloud Foundry resources that run in the IBM Cloud or outside the IBM Cloud by using the IBM Log Analysis service. You can view, filter, search, and analyze these logs through the web UI for a number of days that is determined by the plan of your logging instance. You can also configure archiving, and have access to those logs through the archived files.

Before starting this tutorial you will need to understand Cloud Foundry monitoring concepts and make sure you have the required permissions and prerequisites.



 Understand Cloud Foundry monitoring 

The logs that are generated by Cloud Foundry resources that run on IBM Cloud public are automatically collected and available for monitoring through the IBM Log Analysis instance that is provisioned in the same region, and that is enabled to collect service platform logs. Alternatively, you can choose to configure a custom user provided (CUPS) service for your app, so system and application logs are collected through a custom logging instance.

Zoom

![Monitor Cloud Foundry resources in IBM Cloud Public](https://cloud.ibm.com/docs-content/v1/content/1e0945ee44f87283927af9404a8f2d077786db0c/cloud-foundry-public//images/components-cf-public.svg)

Figure 1. Monitoring Cloud Foundry resources in IBM Cloud Public

If your Cloud Foundry resources run on IBM Cloud dedicated or outside the IBM Cloud, you can configure a custom user provided (CUPS) service for your app, so system and application logs are collected and streamed to a custom logging instance.

Zoom

!
: Each Code Engine project must be configured with a set of [IAM Access policies](https://cloud.ibm.com/docs/account?topic=account-userroles), which authorizes Code Engine service bindings to view service instances and to view and create service credentials in your account. IAM policies are provided to Code Engine service binding with a service ID. For more information, see [Configuring access for service bindings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-configure-bindaccess).

Is there a way to configure service binding operations for all users in a project?
: Yes! With sufficient permissions, you can use the Integration page in the console to configure service binding operations from a single page. If you don't have sufficient permissions to perform these actions, you can use this page to help you understand the required permissions. See [Configuring project-wide settings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrations).

After binding my Code Engine workload to a service instance, what's the life of this service binding?
: When you create a binding between your Code Engine workload and a service instance, the service binding is active as long as the Code Engine workload and the service instance is active, or you haven't completed an unbind operation to remove the service binding. If the service instance is deleted, you'll need to manually delete the service binding. When you unbind (or remove) a service binding, you are deleting the association of the app or job with the service access secret such that the app or job no longer has access to previously bound IBM Cloud service.





 Accessing a bound service instance from a Code Engine workload
In addition to having the right Classic Infrastructure permissions for deploying the underlying hardware devices, users need the right level of Platform Management permissions in order to work with the VMware service instance (i.e. who can see provisioned VMWare instances, who can delete an instance, etc). Please refer to the following asset to understand the required platform management roles:



* [Configuring Platform Management Roles for VMware Service](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-iam)







 Setup Resource Group 

Resource Groups allow you to organize the resources/instances into groups (i.e. ProjectA_Resources, ProjectB_Resources, Dev_Env, Prod_Env, etc.), and can be used as part of the access management strategy (i.e. Developers granted access to resources in Dev_Env resourcce group but no access to Prod_env). When a VMware instance is provisioned, it must be placed within a resource group. Please refer to the follow assets to understand the best practices for using resource groups:



* [Best practices for resource groups and assigning access](https://cloud.ibm.com/docs/account?topic=account-account_setup)







 Create a Classic Infrastructure API Key 

The VMware solution described in this guide will be deployed on Classic Infrastructure (not VPC), so you need to have a Classic Infrastructure API associated with your IBM Cloud Userid. The key is used as part of the provisioning process (i.e. provisioning the underlying bare metals on Classic Infrastructure where VMware will be running).

The steps to configure your Classic Infrastruture API key can be found in the [documentation](https://cloud.ibm.com/docs/account?topic=account-classic_keyscreate-classic-infrastructure-key).





 Next Steps 

The next step on the deployment journey is:



* [Order vCenter Server](https://cloud.ibm.com/docs/vmware-classic-journey?topic=vmware-classic-journey-vmware-onboarding-order-cluster-storage)
* To display the logs of all the instances of your job run, use the [ibmcloud ce jobrun logs --jobrun JOBRUN_NAME](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-logs) command; for example,

ibmcloud ce jobrun logs --jobrun myjobrun

Example output

Getting logs for all instances of job run 'myjobrun'...
Getting jobrun 'myjobrun'...
Getting instances of jobrun 'myjobrun'...
OK

myjobrun-1-0/myjobrun:
Hi from a batch job! My index is: 1

myjobrun-2-0/myjobrun:
Hi from a batch job! My index is: 2

myjobrun-3-0/myjobrun:
Hi from a batch job! My index is: 3

myjobrun-4-0/myjobrun:
Hi from a batch job! My index is: 4





For more information, see [Viewing job logs with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-joblog-cli).





 Getting system event information for my jobs 

System event information can be helpful to troubleshoot problems when you run jobs. You can view system event information with the CLI.

You can display system events of all the instances of a job run or display system events of a specific instance of a job run.



1. Use the [ibmcloud ce jobrun list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-list) command to list all your defined job runs; for example,

ibmcloud ce jobrun list
2.
FAQs: Veeam backup and replication 



  Can I add extra license packs to my Veeam server? 

Yes. If you need to add more license packs to your Veeam backup and replication server, open a sales ticket to start the process.





  Can I add Veeam backup and replication to my existing server? 

Unfortunately it is not possible to add the Veeam backup and replication application to an existing server. You need to either order Veeam when you create the server or issue an OS Reload and add the Veeam backup and replication offering during the reload process.
* [Customizing the service](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-service-featuresfeatures-customization) describes the more advanced topics of language model and acoustic model customization, which can help you gain the most from the service's capabilities. The section also presents grammars, which you can use with language models to limit possible responses to precise strings and phrases.
* [Using software development kits](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-service-featuresfeatures-sdks) provide links to the SDKs that are available to simplify application development in many programming languages.
* [Learning more about application development](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-service-featuresfeatures-learn) provides links to help you get started with Watson services and understand authentication.
Getting started with IBM Cloud Monitoring 

IBM Cloud® Monitoring is a cloud-native, and container-intelligence management system that you can include as part of your IBM Cloud architecture. Use it to gain operational visibility into the performance and health of your applications, services, and platforms. It offers administrators, DevOps teams and developers full-stack telemetry with advanced features to monitor and troubleshoot, define alerts, and design custom dashboards. In architectures that are focused on container and microservices, you can use Secure to protect, monitor, and enhance forensic analysis of your pipeline and runtime components.



 Before you begin 

You must have a user ID that is a member or an owner of an IBM Cloud account. To get an IBM Cloud user ID, go to: [Registration](https://cloud.ibm.com/login).

Check the regions where the service is available. [Learn more](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpointsendpoints_regions).

Read the About section:



* [Monitoring topic](https://cloud.ibm.com/docs/monitoring?topic=monitoring-about-monitor) to understand more about the Monitoring service.
* [Collecting metrics](https://cloud.ibm.com/docs/monitoring?topic=monitoring-about-collect-metrics) to understand more about how to collect metrics.



You can complete the getting started steps in any of the supported regions.





 Step 1. Manage user access 

Every user that accesses the IBM Cloud Monitoring service in your account must be assigned an access policy with an IAM user role defined. The policy determines what actions the user can perform within the context of the service or instance you select. The allowable actions are customized and defined as operations that are allowed to be performed on the service. The actions are then mapped to IAM user roles. For more information, see [Managing user access in the IBM Cloud](https://cloud.ibm.com/docs/monitoring?topic=monitoring-iamiam).

When a user is granted permissions in the IBM Cloud to work with the IBM Cloud Monitoring service, the user is automatically granted a service role.
For example, if your job subscribes to delete changes on an Object Storage bucket and that bucket is deleted, a job is run for each object that was in that bucket and you can quickly reach your limitation of 100 job runs. Additionally, you need to consider the runtime for each job run that is triggered by an event. For example, if your event producer triggers 10 or more events per second and each job runs for about 20 seconds, your job run limit of 100 is reached in about 10 seconds and any subsequent job runs are lost until the previously started job runs are completed. Choose a job as an event subscriber destination only if the number of incoming events is generally low and the peak number of events expected in a specific timeframe is low enough to keep the number of running jobs below the quota limit. For more information, see [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).

After 10 minutes, job runs that are created by subscriptions are deleted. For more information, see [Where is my job run?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-jobrun-deleted).

All events that are delivered to jobs are received as environment variables. For more information, see [Example environment variables for an IBM Cloud Object Storage event that is sent to a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-envvars-job).





 Eventing metadata 

Events that are managed by Code Engine when you create a subscription are modified so that they adhere to the [CloudEvents specification](https://cloudevents.io). This specification defines a set of common attributes that can be included with each event to provide a common set of metadata. By looking at the metadata, you can quickly understand key pieces of the message without parsing and understanding the entirety of the event payload. For example, each event that is delivered to an application includes an HTTP header that is called ce-type, which indicates the semantic meaning (or "reason") for the event.
* Understand the [limitations](https://cloud.ibm.com/docs/vpc?topic=vpc-limitations-vpe) of having a VPE.
* Ensure that you have [created](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-endpoint-gateway) and understand how to [access](https://cloud.ibm.com/docs/vpc?topic=vpc-accessing-vpe-after-setup) a VPE gateway.
* Understand how to [view details](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-viewing-details-of-an-endpoint-gateway) of a VPE.



You may need to manually update VPE settings, specifically the IP address, during disaster recovery and business continuity actions.





 Virtual Private Service Endpoints 

The following table lists regions where VMware as a Service supports VPE. The table also provides VMware as a Service endpoints supported from each region. You can connect to VMware as a Service in another region using supported endpoints.

When connecting to a VPE using [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-endpoint-gatewayvpe-ordering-cli) or [API](https://cloud.ibm.com/docs/vpc?topic=vpc-ordering-endpoint-gatewayvpe-ordering-api), you must specify the Cloud resource name of the region that you use to connect to VMware as a Service. Use the following table to locate the Cloud resource name of the target region.



Table 1. Private endpoints for interacting with VMware as a Service APIs over the IBM Cloud private network

 Region Supported endpoints Cloud resource name 

 Dallas api.private.us-south.vmware.cloud.ibm.com crn:v1:bluemix:public:vmware:us-south:::endpoint:api:private.us-south.vmware.cloud.ibm.com
Why can't I log in immediately after I create an account? 

If your account is still pending, you can't log in to IBM Cloud®.

  What’s happening 

After you create an IBM Cloud account, you might not be able to log in to IBM Cloud. The Your account is pending message might be displayed.

  Why it’s happening 

When you sign up for an IBM Cloud account, you receive an email that includes a confirmation link. You must click this link to confirm your account. If you don't confirm your account, the account remains in a pending state.

  How to fix it 

The confirmation email is sent to the email address that is associated with your IBMid. If you cannot find the confirmation email, go to the [IBM Cloud login page](https://cloud.ibm.com/) and try to log in. The following message is displayed:

To complete your registration, check your email.
Can't find the email? Resend.

Click Resend to send another confirmation email to the email address that is associated with your IBMid.

If you receive the email but the confirmation link doesn't work, it might be a problem with your web browser. You can troubleshoot potential browser problems by clearing cache and cookies in the browser, by using a private or incognito window, or by using a browser on a different computer or device.
I have a device to connect Follow the process that is outlined in this topic. 
 I do not have a device to connect [Simulate device data](https://cloud.ibm.com/docs/services/IoT?topic=IoT-sim_device_datasim_device_data). 







 Step 1: Register your device 

Registering a device involves classifying the device as a device type, giving the device a name, and providing device information. Then you provide a connection token or accept a token that is generated by Watson IoT Platform.

Tip: You can register your devices one at a time from the [Watson IoT Platform dashboard ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://internetofthings.ibmcloud.com), or you can use the [Watson IoT Platform API ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://docs.internetofthings.ibmcloud.com/apis/swagger/v0002/org-admin.html!/Device_Bulk_Configuration/post_bulk_devices_add) to add multiple devices.

To add a device from the Watson IoT Platform dashboard:



1. In the IBM Cloud console, click Launch on the Watson IoT Platform service details page.

The Watson IoT Platform web console opens in a new browser tab at the following URL:

https://org_id.internetofthings.ibmcloud.com/dashboard//overview

Where org_id is the ID of your Watson IoT Platform organization.
2. In the Overview dashboard, from the menu pane, select Devices and then click Add Device.
3. Create a device type for the device that you are adding.

Each device that is connected to the Watson IoT Platform must be associated with a device type. Device types are groups of devices that share common characteristics.



1. Click Create device type.
2.
Why doesn't the console open when I log in with my IBMid? 

You can't view the console after login.

  What’s happening 

When you log in to the IBM Cloud console by using your IBMid, a login success message is displayed, but you don't return to the IBM Cloud console.

  Why it’s happening 

An issue with the browser is causing you to not return to the IBM Cloud console.

  How to fix it 

Use one of the following options:



*  Close your browser, clear the cache and cookies, then try to log in again.
*  Log in from the [IBM Cloud console](https://cloud.ibm.com/).
Apply an RBAC policy to columns 

This task demonstrates how to select an RBAC policy for an application and apply it to selected columns in a table. You may optionally select an encryption mode on the same columns, to transform the underlying data.

Note:



* Only one RBAC policy can be applied to a column.
* RBAC policies are application-specific and cannot be shared with other applications.
* RBAC policies have a dependency on data types, because only certain Mask Modes can be applied for certain data types. In the Column selector, only compatible RBAC Policies are available to select for each column.
* Editing an RBAC policy affects all columns to which the policy is already applied.



To apply an RBAC policy to columns, do the following:



1. In Data Security Broker Manager, navigate to the Applications dashboard, select an application from the listing, and click Encrypt to access the Schema Builder.
2. In the Tree Menu, select a database, schema, and table. This populates the column selector with available columns.
3. Select columns to define with an RBAC policy.
4. In the Data Protection dropdown menu, select an RBAC policy from the list. RBAC policies have a dependency on data types, because only certain Mask Modes can be applied for certain data types. Therefore, in the Column selector, only compatible RBAC Policies are available to select for each column.
5. By default, the standard Encryption mode 'DEFAULT_CTR_DET' is selected.



When an RBAC Policy and encryption mode is selected on the same column, then the underlying database is encrypted as well. To apply an RBAC policy without encrypting, use the Clear Selections option, then select the RBAC policy.



1. Optional: Specify a Key ID for each column from the drop-down menu or accept the default.
2. Click REVIEW at the bottom left panel to review your selections.
3. Review your policy and select a Migration Plan:
4. Save: Saves the data schema for future use.
5.
When you use the private network to pull images, your image pull traffic is not charged as [public bandwidth](https://cloud.ibm.com/docs/containers?topic=containers-costsbandwidth), because the traffic is on the private network. For more information, see the [IBM Cloud Container Registry private network documentation](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_private).

When you set up your IBM Cloud account to use service endpoints, you can use a private network connection to push images to and to pull images from IBM Cloud Container Registry.

What do I need to do to set up my cluster to use the private connection to icr.io registries?



1. Enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account so that you can use the IBM Cloud Container Registry private cloud service endpoint. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command.
2. [Enable your IBM Cloud account to use service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint).



Now, IBM Cloud Container Registry automatically uses the private cloud service endpoint. You don't need to enable the private cloud service endpoint for your IBM Cloud Kubernetes Service clusters.

I have a private-only cluster. How do I enforce that my image traffic remains on the private network?
: The image push and pull traffic is automatically on the private network. IBM Cloud Kubernetes Service can use the public icr.io registry domains in existing image pull secrets to authenticate requests to IBM Cloud Container Registry. These requests are automatically redirected to the private icr.io registry domains. You don't need to modify the image pull secrets or configure additional settings.
Additional services deployed into a Satellite location might have features that require public Internet access. It is recommended to consult the documentation for each service running in a location to verify their connectivity requirements.

If I have two Locations that use Direct Link, can I use them for Direct Link to fail over from one Location to the other?
: This functionality is not yet available.

How do I size Direct Link capacity for my Location?
: There are no additional sizing requirements for using Direct Link. So, you can size your Location like a normal Location, meaning based on the services you will use.

Can I have one-click deployment of everything needed to enable Direct Link to avoid manual errors?
: Currently, a one-click deployment for Direct Link is not available. It might be available at a future time.





 Target use case 

Customers who are currently using Direct Link between IBM and on-prem or other public clouds, can continue to use it for Satellite Link. This allows customers to:



* Access services on IBM Cloud from a Satellite location over Direct Link; examples are backups in IBM Cloud® Object Storage, sending metrics to IBM Cloud Monitoring, tracking events in IBM Cloud Activity Tracker, or sending logs to IBM Cloud Log Analysis.
* Access services running in a Satellite location from IBM Cloud.
* Access public cloud services outside of IBM Cloud.



These can be accessed using Satellite endpoints addresses created to route traffic over Direct Link instead of the internet.

This prevents customer’s sensitive data going over the public internet such as logging, backups or data between integrated services across the hybrid cloud landscape. This also helps optimize ingress/egress charges.





 Overview 

By default, two Satellite Link components, the tunnel server and the connector, proxy network traffic between IBM Cloud and resources in your Satellite location over a secure TLS connection. This document covers the use case of using a TLS connection over Direct Link.

This setup uses the tunnel server's private cloud service endpoint to route traffic over the IBM Cloud private network(166.9.0.0/8, see [Service network](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-ibm-cloud-ip-rangesservice-network).