k8s sidecars for logging yay or nay

we're looking at centralizing our logging in Kubernetes and are considering using sidecar containers for each application pod to handle log collection. the idea is that each app container writes to a local file, and a dedicated sidecar (like Fluentd or Filebeat) picks it up and forwards it. this keeps the application code clean and decoupled from the logging infrastructure. what are your experiences with this pattern? any major gotchas or benefits you've found? are there simpler alternatives you prefer for managing logs in k8s?