Generally there are three configuration workflows in CCO:
To set up your Cisco Cloud Observability, configure Cloud Connections, use OpenTelemetry for instrumentation, and either deploy new OpenTelemetry collectors or configure existing collectors to send data to the Cisco Cloud Observability backend.
Based on your current public cloud deployments, you’ll need to set up a cloud connection to pull data from cloud sources like AWS Cloud Watch, MS Azure Monitor, or Google Cloud Platform. This helps you gain insights into how your cloud infrastructure impacts application performance. To set up your public cloud platform with CCO, you’ll need to supply credentials and any other necessary information for data retrieval.
Additionally you can setup Prometheus or Host Monitoring Data sources.

Note: The AWS Cloud Connection has been pre-configured in your lab environment.
Depending on the current application deployment and OpenTelemetry strategy, you can consider two approaches to start monitoring your Kubernetes cluster and app services:
Before you can start monitoring your application services, you need to analyze your environment and define your workflow:

To successfully deploy Kubernetes Observability, you need to install a set of Kubernetes Operators and OpenTelemetry Collectors on your Kubernetes cluster

You’ll dive right in by setting up your lab environment and integrating instrumentation into the application.