You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "lujie (Jira)" <ji...@apache.org> on 2021/03/22 01:32:00 UTC
[jira] [Updated] (CLOUDSTACK-10432) Audit logging in CloudStack
servers.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lujie updated CLOUDSTACK-10432:
-------------------------------
Description: Lots of users had questions on debugging which client access the CloudStack, like who creates the VM and what updates went through a VM. We should add audit logging as in Hadoop (look at Namenode Audit logging) to log which client changed what in the CloudStack servers. (was: Lots of users had questions on debugging which client access the CloudStack, liking who changed the VM and what updates went through a VM. We should add audit logging as in Hadoop (look at Namenode Audit logging) to log which client changed what in the CloudStack servers. )
> Audit logging in CloudStack servers.
> ------------------------------------
>
> Key: CLOUDSTACK-10432
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10432
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: lujie
> Priority: Major
>
> Lots of users had questions on debugging which client access the CloudStack, like who creates the VM and what updates went through a VM. We should add audit logging as in Hadoop (look at Namenode Audit logging) to log which client changed what in the CloudStack servers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)