Logging

Information regarding the actions performed in Automation Ops™ is recorded in the host portal audit logs.

Each log entry contains the following information:

• the entry category (Governance).
• the user that performed the action (name and email).
• the date and time when the action was performed.
• the action that was performed and a message with details about the action.

See the following table for a list of logged actions and the information that is logged for each one.

Action	Description	Logged Information
Create Policy	A user successfully creates a new policy.	Policy name, product name, policy data, priority, availability.
Edit Policy	A user successfully edits an existing policy.	For both the original policy and the edited policy: name, product name, policy data, priority, availability.
Upload Policy	A user successfully uploads a policy.	Policy name, product name, policy data, priority, availability.
Delete Policy	A user successfully deletes a policy.	Policy name, product name, policy data, priority, availability.
Deploy To Tenant	A user successfully deploys one or more policies at tenant level. Each per-product edit is tracked in a separate log, regardless of whether or not it is the result of a bulk action.	Policy name or No policy / Inherit, license name, product name, tenant name.
Deploy To Group	A user successfully deploys one or more policies at group level. It includes all actions that can affect the deployment settings: editing a group’s deployment settings removing a group deployment (results in Inherit) Each per-product edit is tracked in a separate log, regardless of whether or not it is the result of a bulk action.	Policy name or No policy / Inherit, license name, product name, group name.
Deploy To User	A user successfully deploys one or more policies at user level. It includes all actions that can affect the deployment settings: editing a user’s deployment settings removing a user deployment (results in Inherit) Each per-product edit is tracked in a separate log, regardless of whether or not it is the result of a bulk action.	Policy name or No policy / Inherit, license name, product name, user name.
Edit Version	A user performs a successful upgrade / downgrade of a policy template Each per-product edit is tracked in a separate log, regardless of whether or not it is the result of a bulk action.	Product name, old template version, new template version (major.minor.patch).