Hello, I have tried to reproduce the json_console_...
# ask-community
m
Hello, I have tried to reproduce the json_console_logger example here https://docs.dagster.io/concepts/logging/loggers#customizing-loggers to setup my custom logger for a pipeline. However, when executing the pipeline locally I see no effect, ie, it still uses the default logger. There is no error though. Any idea what could be going wrong?
I can see from the solid context at run time that the associated mode definition is picked up correctly. But the logger is somehow ignored
Any feedback on this?
a
this is when providing the associated
run_config
to select the logger?
m
so I select the mode and when debugging I can see that the mode (and associated logger) is picked up correctly
but seemingly with no effect
a
Copy code
loggers:
  my_json_logger:
    config:
      log_level: INFO
m
the level is optional and set to INFO
so no need to pass it explicitly?
a
you may still need
Copy code
loggers:
  my_json_logger:
to enable the logger
m
mmmm
I see
I have not done that
I though that it’d have been picked up as default logger
let me try again
by the way
I had cases where a solid dies with no clear reason (no meaningful exception) and for the same the UI is not able to load the logs
this is one that produces a significant amount of (debug) messages
a
that sounds like a machine / process crash - if nothing got reported it means our cleanup code didnt have a chance to run which generally indicates a hard crash
m
ok, will start with monitoring the resources
thanks!