Mark Fickett04/22/2022, 1:46 PM
in an application I'm porting to Dagster. They make use of a logging filter as well as file handlers. Is there a way to make my
call get along with Dagster logging setup? I can use the
to capture their output into Dagit, but that only works if I remove the
call. I see that I could add handlers and formatters via
as described in the docs, but it's a little painful to port my current logging config dict setup to
, and I would also lose the filters.
johann04/22/2022, 5:37 PM
owen04/22/2022, 5:39 PM
Mark Fickett04/22/2022, 5:42 PM
which will apply to the root logger, but then I'm guessing they'll catch the
logger output too?
I guess a short-term help would be some more detail about how logs are set up -- when Dagster's logging config is applied, how the
logger is configured (with propagation, any other key details).
owen04/25/2022, 4:59 PM
Mark Fickett04/27/2022, 8:31 PM
, but it seems like they're getting a pre-formatted version. For example, the
is "_battery_data_job_local - 17f7577a-d149-4c4d-82fb-8fba5e810198 - data_pipe_graph_sasquatch_reactor.raw_data_graph_sasquatch_reactor._normalize_arbin8_task_sasquatch_reactor[ananke] -_ Normalizing..." where I would like it to just be "Normalizing..." (all the italicized stuff is added by Dagster).
It looks like this is coming from
property in place: https://sourcegraph.com/github.com/dagster-io/dagster/-/blob/python_modules/dagster/dagster/core/log_manager.py?L232 . And it happens to be handling the particular
before my handler gets to it. If I edit the source to skip that line then I get what I want.
Any way to work around it? Or potentially something that could be changed?
owen04/28/2022, 4:16 PM
(definitely not the most convenient thing, I'll admit)
Mark Fickett04/29/2022, 1:55 PM