[
https://issues.apache.org/jira/browse/AIRFLOW-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Silk updated AIRFLOW-3171:
----------------------------------
Description:
Regardless of the backend (eg file system, s3, ...), it would be useful to be
able to organize the logs by owner.
One use case of this would be to provide a better multi-tenancy experience when
deploying a single airflow cluster to several teams. 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 access rules prefixed with the owner
string.
I also think that this would be a good change regardless of the multi-tenancy
aspect, just in terms of organizing logs (vs the current flat namespace).
was:
Regardless of the backend (eg file system, s3, ...), it would be useful to be
able to organize the logs by owner.
One use case of this would be to provide a better multi-tenancy experience when
deploying a single airflow cluster to several teams. If the log folders in s3
were organized like /tasks/[owner]/... then we could provide access to a subset
of the logs for each time, by creating s3 access rules prefixed with the owner
string.
I also think that this would be a good change regardless of the multi-tenancy
aspect, just in terms of organizing logs (vs the current flat namespace).
> Organize logs by owner
> ----------------------
>
> 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 to be
> able to organize the logs by owner.
>
> One use case of this would be to provide a better multi-tenancy experience
> when deploying a single airflow cluster to several teams. 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 access rules prefixed with
> the owner string.
>
> I also think that this would be a good change regardless of the multi-tenancy
> aspect, just in terms of organizing logs (vs the current flat namespace).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
