[GitHub] [airflow] uranusjr commented on a diff in pull request #32269: Clarify Listener API behavior

["uranusjr (via GitHub)" <gi...@apache.org>]

uranusjr commented on code in PR #32269:
URL: https://github.com/apache/airflow/pull/32269#discussion_r1250484075


##########
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 prints will be handled as part of the listeners.

Review Comment:
   ```suggestion
   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.
   ```
   
   For further clarity?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org