Deploy the Log Collector

Overview

To deploy the Log Collector onto your cluster, set log-specific parameters in the Kubernetes and App Service Monitoring Helm chart's "values override" file, collectors-values.yaml, and then apply the changes to your cluster.

Prerequisites

If you have an existing deployment of Kubernetes and App Service Monitoring or the Log Collector, follow any migration steps or required actions described in Release Notes.

Ensure that your environment conforms to the Kubernetes and App Service Monitoring Software Requirements.
Confirm your environment meets the specific Log Collector Requirements.
You must first deploy Kubernetes and App Service Monitoring. See Install Kubernetes and App Service Monitoring.
If Filebeat is running on your cluster, uninstall it. You cannot use an existing Filebeat deployment with the Log Collector.
On your cluster, ensure that the log-generating applications are already running.

Set Log-Specific Parameters

Locate the same "values override file" that you used to deploy Kubernetes and App Service Monitoring. If you aren't sure which file that is, see Recover a Lost Values YAML File.
Set logs-specific parameters in the "values override file", collectors-values.yaml. See Configure the Log Collector.
If you're deploying the Log Collector on Windows nodes on Google Kubernetes Engine (GKE), add the following tolerations to appdynamics-cloud-k8s-monitoring.logCollectorPod:
(GKE does not allow usage of kubernetes.io/os: windows label as node selector while deploying the Windows host process pods. Therefore, to deploy the Log Collector pods on GKE, you must include this toleration):
```
 appdynamics-cloud-k8s-monitoring:   
  logCollectorPod:
    tolerations:  
      - key: "node.kubernetes.io/os"
        operator: "Equal"
        value: "windows"
        effect: "NoSchedule" 
```
YML
node.kubernetes.io/os=windows:NoSchedule is a default taint added on Windows nodes in GKE. If there are any additional taints on your Windows nodes, see Monitor the Tainted Nodes.

Apply Changes to Your Cluster

To apply the modified collectors-values.yaml to your cluster, follow the "Upgrade Collectors" steps in Upgrade or Uninstall Kubernetes and App Service Monitoring. This deploys the Log Collector as a DaemonSet (one instance per node) onto your cluster.
Verify that all Log Collector pods are running on your cluster and your logs are visible. See Verify the Log Collector Deployment.
If your logs appear on Cisco Cloud Observability but are unparsed or incorrectly parsed, see Log Parsing Validator.