One way to send logs to Cisco Cloud Observability is to deploy the Log Collector onto supported Kubernetes® clusters. The Log Collector is a modified and enhanced version of Filebeat with an OpenTelemetry™ Line Protocol (OTLP) codec and exporter. It's an optional component of Kubernetes and App Service Monitoring.
How Log Collection Works
The Log Collector harvests log messages from your cluster's microservices, applications, and infrastructure, parses them, enriches them with metadata, converts them into OTLP packets, and sends the OTLP packets to AppDynamics Distribution for OpenTelemetry™ Collector, which forwards them to the Common Ingestion Service. Once ingested, they're retained for 30 days and searchable on the Logs page. The Log Collector handles send errors and retries operations as needed.
The Log Collector does not filter or scrub out any sensitive data present in log messages.
Deployment Overview
To deploy the Log Collector onto your cluster, you set logs-specific parameters in the Kubernetes and App Service Monitoring Helm chart. At a minimum, you specify log location, log type, and log message pattern. To apply the modified Helm chart to your cluster, you run a helm command. This command deploys the Log Collector as a DaemonSet (one instance per node).
Next Step
Log Collector Requirements
This document contains references to OpenTelemetry™ documentation. Splunk AppDynamics does not own any rights and assumes no responsibility for the accuracy or completeness of such third-party documentation.
OpenTelemetry™ and Kubernetes® (as applicable) are trademarks of The Linux Foundation®.
