Hi! is there any way I can fetch the run_id without having access to the 'SolidExecutionContext'?

could you add more detail about where you are where a

run_id

would exist but you dont have access to the

context

?

I'm not sure what's the best practice, but basically I need to attach 'run_id' to every single log message in my app. This will require me to change the signatures of every function that needs to log (to accept context as a param). Is there maybe an easier way to retrieve the current context?

Not currently, but it is a reasonable request. Could you file an issue? cc @chris In the mean you could set your own process global /

ContextVar

from an op or resource

I’m not sure if we already have an issue for pulling a context out of thin air but I can make one if not

you can use the get_dagster_logger function to get a logger that will log messages w/ all the dagster context info (run_id, step key, job name, etc.) on it. It won't give you direct access to the context object, but if you just need the run_id to be in the log messages, that should work for you.