Assigned
Status Update
Comments
va...@google.com <va...@google.com>
je...@google.com <je...@google.com> #2
This feature request has been forwarded to the Data Fusion engineering team so that they may evaluate it. Note that there are no ETAs or guarantees of implementation for feature requests. All communication regarding this feature request is to be done here.
Description
Problem you have encountered:
I had a python flex template pipeline that was failing to start the worker using my custom SDK image, and finding the error in the logs was made much harder by the fact that everything was logged at "default" log level, even log.fatal() calls in beam's boot.go.
What you expected to happen:
Fatal logs should be logged at error severity, etc.
Steps to reproduce:
Modify a worker SDK image's entry point to eat up the argv, e.g. by wrapping in a call to bash:
ENTRYPOINT["/bin/bash", "-c", "/opt/apache/beam/boot"]
The worker will then not get the "id" argument passed and will log fatal on startup (https://github.com/apache/beam/blob/master/sdks/python/container/boot.go#L108 )
Go to logs explorer and run query:
And observe lines like "2025/01/28 22:14:30 No id provided." at default severity.
JSON Payload omitting our project-specific info:
I believe this is also the case for log.Warning's, e.g. the following lines in logs explorer at info severity:
Which ultimately gets logged athttps://github.com/apache/beam/blob/3d4615e2fe916d5cb92763736a97b1573d36f2ba/sdks/python/apache_beam/typehints/decorators.py#L375
(fromhttps://github.com/apache/beam/blob/3d4615e2fe916d5cb92763736a97b1573d36f2ba/sdks/python/apache_beam/typehints/decorators.py#L329 )