umber of multiple runs), and
>> each unit should have a unique key or location. One of the reasons we are
>> working on this effort is to actually make Airflow play nicer with
>> Kubernetes/Docker (since airflow workers should ideally be ephemeral), and
>> allowing a separate service to
d
> allowing a separate service to read and ship the logs is necessary in this
> case since the logs will be destroyed along with the worker instance. I
> think in the future we should also allow custom logging modules (e.g.
> directly writing logs to some service).
> >
> &g
> service to read and ship the logs is necessary in this case since the logs
> will be destroyed along with the worker instance. I think in the future we
> should also allow custom logging modules (e.g. directly writing logs to some
> service).
>
>
> On Wed, Jun 21, 2017 at 3:11
s will be destroyed along with the worker instance. I
think in the future we should also allow custom logging modules (e.g.
directly writing logs to some service).
On Wed, Jun 21, 2017 at 3:11 PM, Allison Wang <allisonwang...@gmail.com>
wrote:
> Hi,
>
> I am in the proces
Sent: 01 February 2017 12:55:42
To: dev@airflow.incubator.apache.org
Subject: Re: Airflow Logging Updates
Hey Robin,
I also have an interest in logging, but to get Google Cloud logging to
work. I'm happy to work with you on this. But *first* the 1.8 needs to go
out.
But I don't think this wi
Hey Robin,
I also have an interest in logging, but to get Google Cloud logging to
work. I'm happy to work with you on this. But *first* the 1.8 needs to go
out.
But I don't think this will go on the patch branch, but maybe for the next
release. I don't know what the other people think.
On Wed,
Hi All,
A while ago we took over this issue:
https://issues.apache.org/jira/browse/AIRFLOW-409, which revolved around
avoiding making changes to the root python logging configuration so as to avoid
any accidental side effects that this could produce in other python
applications.
The
> From: Maxime Beauchemin <maximebeauche...@gmail.com>
> Sent: 14 October 2016 17:02
> To: dev@airflow.incubator.apache.org
> Subject: Re: Airflow Logging
>
> Another consideration is for configuration as code in `settings.py`
> in-place or in conjunc
gmail.com>
Sent: 14 October 2016 17:02
To: dev@airflow.incubator.apache.org
Subject: Re: Airflow Logging
Another consideration is for configuration as code in `settings.py`
in-place or in conjunction with `airflow.cfg` to allow more dynamic
configuration, like passing your own custom log hand
wyman.com/>
From: Maycock, Luke
Sent: 13 October 2016 14:52
To: dev@airflow.incubator.apache.org
Subject: Airflow Logging
Hi All,
We (owlabs - fork: https://github.com/owlabs/incubator-airflow) have a high
level design for how to improve the logging throughout the Airflow code to be
mor
Hi All,
We (owlabs - fork: https://github.com/owlabs/incubator-airflow) have a high
level design for how to improve the logging throughout the Airflow code to be
more consistent, maintainable and extensible. We'd really appreciate any
feedback on the design.
Design for Consolidating Logging
11 matches
Mail list logo
