You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Vira Vitanska (Jira)" <ji...@apache.org> on 2020/04/24 08:34:00 UTC
[jira] [Assigned] (DLAB-1707) [Back-end]: Implement audit by DLab
level
[ https://issues.apache.org/jira/browse/DLAB-1707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vira Vitanska reassigned DLAB-1707:
-----------------------------------
Assignee: Oleg Fuks
Labels: AWS AZURE Back-end Debian GCP RedHat (was: AWS AZURE Debian GCP RedHat)
Summary: [Back-end]: Implement audit by DLab level (was: Implement audit by DLab level)
> [Back-end]: Implement audit by DLab level
> -----------------------------------------
>
> Key: DLAB-1707
> URL: https://issues.apache.org/jira/browse/DLAB-1707
> Project: Apache DLab
> Issue Type: New Feature
> Components: DLab Main
> Reporter: Vira Vitanska
> Assignee: Oleg Fuks
> Priority: Major
> Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
> Fix For: v.2.4
>
>
> Possibility to find out:
> * Who has deleted or added user?
> * Who has created notebook/compute?
> * Who has stopped/started/terminated notebook/compute/project?
> * Who has edited group/project/notebook/compute?
> * Who has gone to links?
> * When changes have been made
> * What changes have been made?
> In general everything that has been done via DLab UI should be in history of changes.
> History by changes should be in the following consistency:
> user → time→ action.
> This functionality should be conveyed to a new tab 'Audit'.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org