Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Audit logs for your team that manages operations help the IT administrators and Atlassian support teams troubleshoot integrations and issues related to configuration changes. Audit logs are accessible to only the admins (organization, site, or product, or team) and members of the team that are given additional permissions to view them.Audit logs is ). If you’re a team admin, contact the admin for your organization, site, or product for access permissions.

Audit logs is the best place to go to view all the incoming data related to your integrations and configuration updates , or if you’re having trouble with your integrations for your team that’s managing operations.

...

Audit logs are maintained, by default, for one year180 days.

Understanding audit logs

Audit logs capture and provide key information on what activity was performed and its outcomethe activities and their outcomes. They are broadly categorized into two groups and further into sub-categories.

...

The log category tells you whether the record relates to a notification, alert, integration and so on, etc.

Jira Service Management System Actions: Captures information about system-originated actions (incoming data and automation).

Jira Service Management User Actions: Captures information about user-originated activity in the following areas. For example, configuration changes at a product

...

or integration level, project settings, assets (global schemas, reference, status, icons)

...

Jira Service Management User Actions: Captures information about user-originated activity in the following areas. This , etc. The following isn’t an exhaustive list, but it gives you an idea of what is covered.

  • Alerts

  • API

  • Integrations

  • Emails

  • HeartbeatsIncidents

  • Notifications

  • On-call schedulesUser management

An activity could be a create/change/delete action taken in relation to any of these entities.

Expand
titleLog categories

Category

For logging ..

Integration

Changes related to integrations

Alert and alert action

Changes related to alerts and alert actions

API request

Changes related to API payloads

Email request

Changes related to email workflows

Config change

Changes related to configuration

Notification

Changes related to notifications

Log levels

There are five three logging levels available in audit logs:

  • INFORMATION (including DEBUG and TRACE): The most verbose logging. Indicates what’s generally happening in the environment.

  • WARNING: 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
titleLog attributes and examples

Attribute

Example

Time stamp Timestamp and timezone

Mar 08, 2023 16:24 GMT+5:30

Category

Integrations, Alerts, Configuration changes

Activity summary

[outgoing][alert] Received integration request with event ID: [a4a89a81-386c-489b-a897-a1bd72035884], but there are integration(s) that are turned off.

[alertAction] User [xyz@mysite.com] is added as a responder via web.

Log level

INFORMATION

WARNING

ERROR

Logs in JSON format

Image Added