[GitHub] [airflow] joshi95 opened a new issue #10125: Dags api /dags//dag_runs currently support only status as an extra key argument in get api. Support for not only status but other fields also for eg execution_date, run_id etc.

[GitBox <gi...@apache.org>]

joshi95 opened a new issue #10125:
URL: https://github.com/apache/airflow/issues/10125


   Registering this as a feature that can help people keep track of job run via api better.
   
   **Description**
   
   <!-- A short description of your feature -->
   
   Currently users can only get the status of a dag run via checking the state of the sepecific dag runs or get all the status of a dag which seems very costly on users front.
   
   Support for this feature will allow users to filter out dags in the dag get runs api and get specific response based on other filters. 
   
   **Use case / motivation**
   Will help users to monitor or get the status of the dag in deep down level and they can use some polling based mechanism to check the health of the runs of the dag.
   
   


----------------------------------------------------------------
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.

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

[GitHub] [airflow] boring-cyborg[bot] commented on issue #10125: Dags api /dags//dag_runs currently support only status as an extra key argument in get api. Support for not only status but other fields also for eg execution_date, run_id etc.

[GitBox <gi...@apache.org>]

boring-cyborg[bot] commented on issue #10125:
URL: https://github.com/apache/airflow/issues/10125#issuecomment-667895857


   Thanks for opening your first issue here! Be sure to follow the issue template!
   


----------------------------------------------------------------
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.

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

[GitHub] [airflow] eladkal closed issue #10125: Better status monitoring in dag job runs api

[GitBox <gi...@apache.org>]

eladkal closed issue #10125:
URL: https://github.com/apache/airflow/issues/10125


   


-- 
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

[GitHub] [airflow] eladkal commented on issue #10125: Better status monitoring in dag job runs api

[GitBox <gi...@apache.org>]

eladkal commented on issue #10125:
URL: https://github.com/apache/airflow/issues/10125#issuecomment-962415929


   This request was raised against the experimental API which is no longer enhanced.
   In the Rest API the dagrun endpoint require a run_id as you mentioned in your example.
   
   If something is still missing please open a new issue about the rest api and explain the use case.


-- 
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