Page Comparison

Overview

Audit logs for your team that manages operations help the IT administrators and Atlassian support teams troubleshoot integrations and issues related to configuration changes. The admins of your orgAudit logs are accessible to only the admins (organization, site, product, or team) and team can access the audit logs. Team admins get a summary of all logs associated with an integration so that they can troubleshoot.Search your logs using Log page and you can find details of your history.members of the team that are given additional permissions to view them.

What are audit logs used for?

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.

Troubleshooting integration data flows follows this pattern:

• Check the logs of the originating system to verify that a request is made.

• Check the audit logs to verify that the request is received.

• If the request is received, look into how it was processed.

• If the request isn’t received, check the configuration on the sender’s side.

Understand audit logs

Audit logs provide information on what activity was performed and its outcome. They are categorized into two sets at a high level and further into sub-categories.

Log 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. 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:

  • Alerts

  • Integrations

  • Incidents

  • Notifications

  • User management
    An activity could be a create/change/delete action taken upon in any of the following:

    • Integrations

    • Alerts

    • Service requests

    • Incidents

    • Problems

    • Changes

    • On-call schedules

    • Reports

    • Knowledge base

    • Heartbeats

    • Post-incident review

    • Dashboards

Log levels

There are five logging levels available in audit logs:

• INFO (including DEBUG and TRACE): The most verbose logging

• WARN: The default level

• ERROR (includes FATAL): The least verbose logging

Audit log attributes and examples

The following table lists the primary log attributes every log entry comprises and provides examples for each: