Audit logs
You can access and export audit logs. Audit logs contain many changes that occur inside of your piplanning app account. Changes occur when a user or service within your account takes an action.
Audit events can be the following occurrences:
CRUD of stickies
CRUD of users and teams
changes to stickies triggered by your connected ALM tool(s)
and much more
Access audit log
In the Cockpit you can download audit-logs. You need to be an administrator to do so. The logs can be downloaded under Settings as an xlsx file.
Review audit log
You can only get events of the last 60 days.
Audit event information
| Information / Column | Details |
|---|---|
| timestamp | UTC timestamp |
| service | On which internal service the event was triggered |
| triggered_by | If the service can know, it indicates which source triggered the change. Can be -, User or ALM |
| action | Event-type. E.g. 'sticky_alter', 'authorized', 'user.jwt-revoke'... |
| data | More data for the event. Can be parameters or metadata |
| session_id | Lists the piplanning-session ID if the action happens in a piplanning session |
| object_id | Lists the object ID if the action happens on a particular object (e.g. Sticky-note) |
| authid | If the change is triggered by a user, it lists the user-id. Can be in two formats: <tenant-id>.<user-id> or <user-id> |
| board_id | Lists the board ID if the action happens on a particular piplanning app board |
Practical examples
Authentication of a user
Authentication of users are found on the 'service=authserver; action=authorized' event. The authid of the event can be useful to track changes of that user in further events. More details can be found in the data property: IP (x-real-ip), user-agent and so on.
Prior the authorized event, another one ('service=authserver, action=user.login.success') is listed. It lists the users email in data besides the authid.