Is your feature request related to a problem? Please describe.
Though the documentation explains how to BYO logger and gives the impression it supports structured logging, the run task web logs only show the message and no extra fields. This makes it unclear if the user mounted their logger improperly or if there's actually an issue. The documentation also encourages interpolating your log values into the message name, which is not the preferred way to use structured logs.
Example
Notice no way to see the extra metadata on the logs:
Describe the solution you'd like
Add a UI spot to show the extra metadata on the log.
Describe alternatives you've considered
The documentation suggests interpolating some of your handpicked values into the logs, but this becomes annoying if you're already doing structured logging in the rest of the app, so you either slam a whole JSON payload in or have to rethink how you want to do logging for these tasks.
Additional context
Example implementation UI:
Is your feature request related to a problem? Please describe.
Though the documentation explains how to BYO logger and gives the impression it supports structured logging, the run task web logs only show the message and no extra fields. This makes it unclear if the user mounted their logger improperly or if there's actually an issue. The documentation also encourages interpolating your log values into the message name, which is not the preferred way to use structured logs.
Example
Notice no way to see the extra metadata on the logs:
Describe the solution you'd like
Add a UI spot to show the extra metadata on the log.
Describe alternatives you've considered
The documentation suggests interpolating some of your handpicked values into the logs, but this becomes annoying if you're already doing structured logging in the rest of the app, so you either slam a whole JSON payload in or have to rethink how you want to do logging for these tasks.
Additional context
Example implementation UI: