From commits-return-24775-archive-asf-public=cust-asf.ponee.io@airflow.incubator.apache.org Tue Oct 9 03:32:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1DBED18067A for ; Tue, 9 Oct 2018 03:32:03 +0200 (CEST) Received: (qmail 94182 invoked by uid 500); 9 Oct 2018 01:32:03 -0000 Mailing-List: contact commits-help@airflow.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airflow.incubator.apache.org Delivered-To: mailing list commits@airflow.incubator.apache.org Received: (qmail 94171 invoked by uid 99); 9 Oct 2018 01:32:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2018 01:32:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id BCD4E1A1542 for ; Tue, 9 Oct 2018 01:32:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id nZK0M68-FdSP for ; Tue, 9 Oct 2018 01:32:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3A1E55F3B7 for ; Tue, 9 Oct 2018 01:32:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7710AE0A31 for ; Tue, 9 Oct 2018 01:32:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4112C24801 for ; Tue, 9 Oct 2018 01:32:00 +0000 (UTC) Date: Tue, 9 Oct 2018 01:32:00 +0000 (UTC) From: "Gabriel Silk (JIRA)" To: commits@airflow.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AIRFLOW-3171) Flexible task log organization MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AIRFLOW-3171?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabriel Silk updated AIRFLOW-3171: ---------------------------------- Description:=20 Regardless of the backend (eg file system, s3, ...), it would be useful to = be able to organize the task logs=C2=A0in a more flexible manner, rather th= an defaulting to a flat structure. =C2=A0 One use case of this would be to provide a better multi-tenancy experience = when deploying a single airflow cluster to several teams. For example, if t= he log folders in s3 were organized like /tasks/[owner]/... then we could p= rovide access to a subset of the logs for each team, by creating s3 access = rules prefixed=C2=A0with the appropriate path. =C2=A0 One possible implementation would be to have a configurable, templatized pa= th structure for logs. We would also need to store the log location for eac= h task instance, so we could easily change the log folder structure without= breaking old log paths. was: Regardless of the backend (eg file system, s3, ...), it would be useful to = be able to organize the logs=C2=A0in a more flexible manner, rather than de= faulting to a flat structure. =C2=A0 One use case of this would be to provide a better multi-tenancy experience = when deploying a single airflow cluster to several teams. For example, if t= he log folders in s3 were organized like /tasks/[owner]/... then we could p= rovide access to a subset of the logs for each team, by creating s3 access = rules prefixed=C2=A0with the appropriate path. =C2=A0 One possible implementation would be to have a configurable, templatized pa= th structure for logs. We would also need to store the log location for eac= h task instance, so we could easily change the log folder structure without= breaking old log paths. > Flexible task log organization > ------------------------------ > > Key: AIRFLOW-3171 > URL: https://issues.apache.org/jira/browse/AIRFLOW-3171 > Project: Apache Airflow > Issue Type: Improvement > Components: logging > Reporter: Gabriel Silk > Priority: Minor > > Regardless of the backend (eg file system, s3, ...), it would be useful t= o be able to organize the task logs=C2=A0in a more flexible manner, rather = than defaulting to a flat structure. > =C2=A0 > One use case of this would be to provide a better multi-tenancy experienc= e when deploying a single airflow cluster to several teams. For example, if= the log folders in s3 were organized like /tasks/[owner]/... then we could= provide access to a subset of the logs for each team, by creating s3 acces= s rules prefixed=C2=A0with the appropriate path. > =C2=A0 > One possible implementation would be to have a configurable, templatized = path structure for logs. We would also need to store the log location for e= ach task instance, so we could easily change the log folder structure witho= ut breaking old log paths. -- This message was sent by Atlassian JIRA (v7.6.3#76005)