You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2019/04/17 08:04:20 UTC

[GitHub] [airflow] raviagarwalunravel opened a new pull request #5118: [AIRFLOW-4315] Add monitoring API's to airflow

raviagarwalunravel opened a new pull request #5118: [AIRFLOW-4315] Add monitoring API's to airflow
URL: https://github.com/apache/airflow/pull/5118
 
 
   ### Jira
   
   - [ ] My PR addresses the following [AIRFLOW-4315](https://issues.apache.org/jira/browse/AIRFLOW-4315) issues and references them in the PR title .
   
   ### Description
   
   Following endpoint have been added using this PR:
   - GET /api/experimental/dags
   - GET /api/experimental/dags/<DAG_ID>
   - GET /api/experimental/dags/<DAG_ID/tasks
   - GET /api/experimental/dag_runs
   - GET /api/experimental/task_instances
   - GET /api/experimental/dags/<DAG_ID>/dag_runs/EXECUTION_DATE/tasks/<TASK_ID>/logs
   
   Following endpoints have been modified to either improve response or to add more filters:
   - GET /api/experimental/dags/<DAG_ID>/tasks/<TASK_ID>
   - GET /api/experimental/dags/<DAG_ID>/dag_runs
   - GET /api/experimental/dags/<DAG_ID>/dag_runs/<string:execution_date>
   - GET /api/experimental/dags/<DAG_ID>/dag_runs/<EXECUTION_DATE>/tasks/<TASK_ID>
   
   EVERYTHING BELOW IS A WORK IN PROGRESS
   ### Tests
   
   - [ ] My PR adds the following unit tests --> WIP
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
   ### Code Quality
   
   - [ ] Passes `flake8`
   

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


With regards,
Apache Git Services