Clarify Listener API behavior (#32269)

* Fixes: #31180 - Plugin for listeners - on_dag_run_running hook ignored Documentation update for Plugin for listeners - on_dag_run_running hook ignored Co-authored-by: Tzu-ping Chung <[email protected]> (cherry picked from commit ab2c861)
apache · Jul 6, 2023 · 3e4c5e8 · 3e4c5e8
1 parent 555d73c
commit 3e4c5e8
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/apache-airflow/administration-and-deployment/listeners.rst b/docs/apache-airflow/administration-and-deployment/listeners.rst
@@ -54,7 +54,7 @@ Airflow defines the specification as `hookspec <https://github.com/apache/airflo
 
 To include the listener in your Airflow installation, include it as a part of an :doc:`Airflow Plugin </authoring-and-scheduling/plugins>`
 
-Listener API is meant to be called across all DAGs and all operators. You can't listen to events generated by specific DAGs. For that behavior, try methods like ``on_success_callback`` and ``pre_execute``. These provide callbacks for particular DAG authors or operator creators.
+Listener API is meant to be called across all DAGs and all operators. You can't listen to events generated by specific DAGs. For that behavior, try methods like ``on_success_callback`` and ``pre_execute``. These provide callbacks for particular DAG authors or operator creators. The logs and ``print()`` calls will be handled as part of the listeners.
 
 
 |experimental|