mistral/mistral/engine
Vasudeo Nimbekar 88e7e7ceee Adding root_execution_id parameter to mistral loggers
After this patch, user can update logging format to include root_execution_id in logs, which will be helpful to find and debug logs related to specific workflow execution.

  - Logs about creation and status changes of Mistral entities(execution,
    task, action execution, etc) are changed to INFO log level.
  - User can update logging_context_format_string to include root_execution_id in logs.

Implements: Implements: blueprint improve-mistral-loggers

Change-Id: I54fe058e5451abba6ea7f69d03d498d78a90993e
2023-02-13 05:01:39 +00:00
..
__init__.py Renaming "engine1" to "engine" 2015-04-09 17:47:36 +06:00
action_handler.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
actions.py Adding root_execution_id parameter to mistral loggers 2023-02-13 05:01:39 +00:00
base.py Remove usage of six.add_metaclass 2020-09-19 11:37:24 +08:00
default_engine.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
dispatcher.py Performance: remove unnecessary workflow execution update 2018-09-03 11:47:11 +07:00
engine_server.py Add "convert_output_data" config property for YAQL 2020-02-13 17:31:41 +07:00
policies.py Remove six library 2020-09-23 10:27:12 +08:00
post_tx_queue.py Init profiler in for a new thread in post_tx_queue.py 2020-02-07 13:42:55 +07:00
task_handler.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
tasks.py Adding root_execution_id parameter to mistral loggers 2023-02-13 05:01:39 +00:00
utils.py Refactor Mistral with Action Providers 2020-09-24 11:10:33 +00:00
workflow_handler.py Refactor task policies 2020-06-01 14:05:49 +07:00
workflows.py Adding root_execution_id parameter to mistral loggers 2023-02-13 05:01:39 +00:00