Filebeat logging troubleshooting guide

1. Check if labels are present on the service labels: app: voiceai owner: duploservices tenantid: 23440ca9-8ce2-4bfe-8004-a4ceb04f1f5a tenantname: duploservices-prod

2. Check if filebeat pod is present on the host where service is present.

3. Check if application logs are getting stored on a file at the host level. ec2 --> /var/log/containers/container-name.log

4. Check if log file has the container name in it. eg: conatiner-name.log

5. Check whether filebeat is processing the log file kubectl logs -f filebeat-pod -n namespace | grep

6. If everything looked good, try restarting the filebeat pod and check. (This worked for me.)