Will Gunadi
03/22/2022, 2:59 PMalex
03/22/2022, 3:01 PMevent_logs
tableWill Gunadi
03/22/2022, 3:01 PMalex
03/22/2022, 3:09 PMnull
, itll be in the event
col json payloadWill Gunadi
03/22/2022, 4:03 PMalex
03/22/2022, 4:15 PMcontext.log
should result in a row in the event_logs
db with a json serialized EventLogEntry
object in the event
column containing the contents of the logged string in the user_message
field.Will Gunadi
03/23/2022, 9:56 PM"user_message": "Writing file at: /home/de1/dagster_f45/storage/b7066d95-83a8-496e-af7f-5d312cb17838/insights_refresh_time/last_insights_refresh"
alex
03/23/2022, 9:59 PM@op
look like? It appears that this is the context.log.debug
from the fs_io_manager
resource which would correspond to returning a value from your op. If you explicitly logged the value yourself in the op i would expect it to to be in the db directlyWill Gunadi
03/23/2022, 10:09 PM<http://context.log.info|context.log.info>(some_str_var)
alex
03/23/2022, 10:13 PMsome_str_var
? I think you are finding the log entry output by https://github.com/dagster-io/dagster/blame/master/python_modules/dagster/dagster/core/storage/fs_io_manager.py#L117Will Gunadi
03/23/2022, 10:14 PMalex
03/23/2022, 10:20 PMWill Gunadi
03/23/2022, 10:21 PMalex
03/23/2022, 10:21 PMWill Gunadi
03/23/2022, 10:22 PMalex
03/24/2022, 2:10 PMWhy would I need to create a separate table if I can query it right within the context of the value?it’s theoretically possible some future version may change how those logs are stored