Container Observability post installation
After you deploy Container Observability (CO), you can enable optional observability features to extend what CO collects. This section covers those post-installation tasks. Enable the features that match the data you want to bring into CO, such as distributed traces, external logs, or both.
CO tracing
CO tracing connects Container Observability to an application backend to capture distributed traces of requests as they move across your services. You trace a slow request across several microservices to find which service is adding the latency. To view both the standard and external methods to enable CO tracing, see Enable tracing for Container Observability.
CO Splunk log collection
Configures Container Observability to collect logs from an external Splunk instance instead of the default log source. You can correlate application logs already stored in your organization's Splunk alongside CO metrics in one place. See Configuring Splunk log collection for details.