[
https://issues.apache.org/jira/browse/AIRFLOW-5645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950074#comment-16950074
]
ASF GitHub Bot commented on AIRFLOW-5645:
-----------------------------------------
tpilewicz commented on pull request #6316: [AIRFLOW-5645] Precise webserver
status monitoring possibilities in quickstart
URL: https://github.com/apache/airflow/pull/6316
Make sure you have checked _all_ steps below.
### Jira
- [x] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW-5645) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-XXX
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [x] Here are some details about my PR, including screenshots of any UI
changes:
My PR adds details in the quickstart of Airflow, precising that the web UI
can be used to monitor the evolution of state of Task Instances and DAG runs. I
suggest adding this because it is a central feature of Airflow.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
Only adding precisions in the documentation.
### Commits
- [x] 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
- [x] 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
----------------------------------------------------------------
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:
us...@infra.apache.org
> In quickstart, precise how airflow commands can be monitored from web UI
> ------------------------------------------------------------------------
>
> Key: AIRFLOW-5645
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5645
> Project: Apache Airflow
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 1.10.5
> Reporter: Thomas Pilewicz
> Assignee: Thomas Pilewicz
> Priority: Minor
>
> The quickstart suggests to run two airflow commands from the CLI to trigger
> some DAG runs and task instances : airflow tasks run, and airflow dags
> backfill. It states that the status of the jobs will be displayed to the user
> but doesn't mention that the webserver can be used to monitor them.
> I suggest developing this statement to tell the user that he will have
> feedback from the CLI, but can also see the status of his tasks in the web
> UI, which is a significant feature of Airflow.
> I'll send a PR with this formulation if that's OK
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
