...
Audit logs are maintained, by default, for one year.
...
Understanding audit logs
Audit logs capture and provide key information on what activity was performed and its outcome. They are broadly categorized into two sets at a high level groups and further into sub-categories.
...
The log category tells you whether the record relates to a notification, alert, integration and so on.
Jira Service Management System Actions: Captures information about system-originated actions (incoming data and automation). For example, configuration changes at a product level or integration level, project settings, assets (global schemas, reference, status, icons) and so on.
Jira Service Management User Actions: Captures information about user-originated activity in the following areas. This isn’t an exhaustive list but gives you an idea of what is covered.
Alerts
API
Integrations
Emails
AlertsHeartbeats
Incidents
Notifications
On-call schedules
User management
...
There are five logging levels available in audit logs:
INFO INFORMATION (including DEBUG and TRACE): The most verbose logging. Indicates what’s generally happening in the environment.
WARNWARNING: The default level. Indicates that something may have gone wrong, or other messages an admin might be interested in.
ERROR (includes FATAL): The least verbose logging. Indicates that something has gone wrong in the environment.
...
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|