damccorm opened a new issue, #37143: URL: https://github.com/apache/beam/issues/37143
### What would you like to happen? Logging is challenging when done across Dataflow and the local runners, specifically the Go SDK v2.70.0. By default beam's log package forwards to slog. When run on GCP via dataflow, I see that hooks includes "default_remote_logging", which causes beam's logger to be sent to a remote endpoint. Now if I have code which uses beam's logger and slog, then all logs go to the same place when running locally, but different places when on workers. I can't have slog redirect to beam's logger, since that would be a loop if run locally, and the remote logging stuff is not exported from the logger. We should have a single way to configure Beam logging in a way that's consistent regardless of the backend. Right now the Beam log package defaults to passing through to "slog". When it runs on the cloud it has a different behavior where the Beam log package and the slog package do different things. ### Issue Priority Priority: 2 (default / most feature requests should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [x] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
