Skip to content


Prefect enables you to log a variety of useful information about your flow and task runs, capturing information about your workflows for purposes such as monitoring, troubleshooting, and auditing.

Prefect captures logs for your flow and task runs by default, even if you have not started a Prefect Orion API server with prefect orion start.

You can view and filter logs in the Prefect UI or Prefect Cloud, or access log records via the API or CLI.

Prefect enables fine-grained customization of log levels for flows and tasks, including configuration for default levels and log message formatting.

Logging overview

Whenever you run a flow, Prefect automatically logs events for flow runs and task runs, along with any custom log handlers you have configured. No configuration is needed to enable Prefect logging.

For example, say you created a simple flow in a file If you create a local flow run with python, you'll see an example of the log messages created automatically by Prefect:

$ python
16:45:44.534 | INFO    | prefect.engine - Created flow run 'gray-dingo' for flow 
16:45:44.534 | INFO    | Flow run 'gray-dingo' - Using task runner 'SequentialTaskRunner'
16:45:44.598 | INFO    | Flow run 'gray-dingo' - Created task run 'hello-task-54135dc1-0' 
for task 'hello-task'
Hello world!
16:45:44.650 | INFO    | Task run 'hello-task-54135dc1-0' - Finished in state 
16:45:44.672 | INFO    | Flow run 'gray-dingo' - Finished in state 
Completed('All states completed.')

You can see logs for the flow run in the Prefect UI by navigating to the Flow Runs page and selecting a specific flow run to inspect.

Viewing logs for a flow run in the Prefect UI

These log messages reflect the logging configuration for log levels and message formatters. You may customize the log levels captured and the default message format through configuration, and you can capture custom logging events by explicitly emitting log messages during flow and task runs.

Prefect supports the standard Python logging levels CRITICAL, ERROR, WARNING, INFO, and DEBUG. By default, Prefect displays INFO-level and above events. You can configure the root logging level as well as specific logging levels for flow and task runs.

Logging Configuration

By default, Prefect displays INFO-level and above logging records. You may change this level to DEBUG and DEBUG-level logs created by Prefect will be shown as well. You may need to change the log level used by loggers from other libraries to see their log records.

You can override any logging configuration by setting an environment variable using the syntax PREFECT_LOGGING_[PATH]_[TO]_[KEY], with [PATH]_[TO]_[KEY] corresponding to the nested address of any setting.

For example, to change the default logging levels for Prefect to DEBUG, you can set the environment variable PREFECT_LOGGING_LEVEL="DEBUG".

You may also configure the "root" Python logger. The root logger receives logs from all loggers unless they explicitly opt out by disabling propagation. By default, the root logger is configured to output WARNING level logs to the console. As with other logging settings, you can override this from the environment or in the logging configuration file. For example, you can change the level with the variable PREFECT_LOGGING_ROOT_LEVEL.

You may adjust the log level used by specific handlers. For example, you could set PREFECT_LOGGING_HANDLERS_ORION_LEVEL=ERROR to have only ERROR logs reported to Orion. The console handlers will still default to level INFO.

There is a logging.yml file packaged with Prefect that defines the default logging configuration.

You can customize logging configuration by creating your own version of logging.yml with custom settings, by either creating the file at the default location (/.prefect/logging.yml) or by specifying the path to the file with PREFECT_LOGGING_SETTINGS_PATH. (If the file does not exist at the specified location, Prefect ignores the setting and uses the default configuration.)

See the Python Logging configuration documentation for more information about the configuration options and syntax used by logging.yml.

Prefect Loggers

To access the Prefect logger, import from prefect import get_run_logger. You can send messages to the logger in both flows and tasks.

Logging in flows

To log from a flow, retrieve a logger instance with get_run_logger(), then call the standard Python logging methods.

from prefect import flow, get_run_logger

def logger_flow():
    logger = get_run_logger()"INFO level log message.")

Prefect automatically uses the flow run logger based on the flow context. If you run the above code, Prefect captures the following as a log event.

15:35:17.304 | INFO    | Flow run 'mottled-marten' - INFO level log message.

The default flow run log formatter uses the flow run name for log messages.

Logging in tasks

Logging in tasks works much as logging in flows: retrieve a logger instance with get_run_logger(), then call the standard Python logging methods.

from prefect import flow, task, get_run_logger

def logger_task():
    logger = get_run_logger()"INFO level log message from a task.")

def logger_flow():

Prefect automatically uses the task run logger based on the task context. The default task run log formatter uses the task run name for log messages.

15:33:47.179 | INFO   | Task run 'logger_task-80a1ffd1-0' - INFO level log message from a task.

The underlying log model for task runs captures the task name, task run ID, and parent flow run ID, which are persisted to the database for reporting and may also be used in custom message formatting.


Prefect log formatters specify the format of log messages. You can see details of message formatting for different loggers in logging.yml. For example, the default formatting for task run log records is:

"%(asctime)s.%(msecs)03d | %(levelname)-7s | Task run %(task_run_name)r - %(message)s"

The variables available to interpolate in log messages varies by logger. In addition to the run context, message string, and any keyword arguments, flow and task run loggers have access to additional variables.

The flow run logger has the following:

  • flow_run_name
  • flow_run_id
  • flow_name

The task run logger has the following:

  • task_run_id
  • flow_run_id
  • task_run_name
  • task_name
  • flow_run_name
  • flow_name

You can specify custom formatting by setting an environment variable or by modifying the formatter in a logging.yml file as described earlier. For example, to change the formatting for the flow runs formatter:

PREFECT_LOGGING_FORMATTERS_FLOW_RUNS_FORMAT="%(asctime)s.%(msecs)03d | %(levelname)-7s | %(flow_run_id)s - %(message)s"

The resulting messages, using the flow run ID instead of name, would look like this:

10:40:01.211 | INFO    | e43a5a80-417a-41c4-a39e-2ef7421ee1fc - Created task run 
'othertask-1c085beb-3' for task 'othertask'

Log database schema

Logged events are also persisted to the Orion database. A log record includes the following data:

Column Description
id Primary key ID of the log record.
created Timestamp specifying when the record was created.
updated Timestamp specifying when the record was updated.
name String specifying the name of the logger.
level Integer representation of the logging level.
flow_run_id ID of the flow run associated with the log record. If the log record is for a task run, this is the parent flow of the task.
task_run_id ID of the task run associated with the log record. Null if logging a flow run event.
message Log message.
timestamp The client-side timestamp of this logged statement.

For more information, see Log schema in the API documentation.