mdediana opened a new pull request #9354:
URL: https://github.com/apache/airflow/pull/9354


   Airflow provides logging handlers that send logs to external services 
(Elasticsearch, StackDriver, etc). At the moment, if Elasticsearch is in use, 
links to its logs show up in the UI. This PR generalizes this functionality to 
other logging handlers.
   
   To provide links to remote logs, a logging handler must inherit from 
`RemoteLoggingMixin` and implement a `get_remote_log_url()` method and have a 
`REMOTE_LOG_NAME` attribute. The view identifies when a remote logging handler 
is in use and shows the link to the logs in the UI.
   
   This PR does not close but is is related issue #9083.    
   
   ---
   Make sure to mark the boxes below before creating PR: [x]
   
   - [x] Description above provides context of the change
   - [x] Unit tests coverage for changes (not needed for documentation changes)
   - [x] Target Github ISSUE in description if exists
   - [x] Commits follow "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)"
   - [x] Relevant documentation is updated including usage instructions.
   - [x] I will engage committers as explained in [Contribution Workflow 
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   ---
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   Read the [Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)
 for more information.
   


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


Reply via email to