Require information about JIRA Platform Audit API

[swarada_jalukar]

Hello community, 

I was analysing JIRA platform API - /rest/api/3/auditing/record (Get audit records endpoint) and came across few questions:

• How much data volume we can expect for the large size organization for the audit events endpoint?
• At what interval data generated from some activity on the platform is made available at the API endpoint?

Can someone please help me with answers to above questions?

Thanks!

[Nikola Perisic · Accepted solution]

Hi @swarada_jalukar

Question 1:

• The API call for this endpoint would return maximum of 1000 records
• To retrieve more than 1000 records, you need to use pagination by utilizing the nextPageLink provided in the API response

Question 2:

• For data interval, what do you mean by this?

[swarada_jalukar]

Hi @Nikola Perisic ,

Let me elaborate the points, 

Question 1. Let's say for a large-sized organization, what is the typical total number of audit event records that can be retrieved through this API?
In other words, how much amount of data is expected to be generated from large organizations in days/weeks?

Question 2. We need to determine the event generation rate at the API endpoint following user activities. Specifically would they generate in limits like 100 events/second? or 1000 events/second?Higher volumes?

[swarada_jalukar]

Hi @Nikola Perisic , 

can you please help me with above queries. 

[Nikola Perisic]

@swarada_jalukar 

1. Organization size doesn't matter, the amount of API responses will be max 1000

2.No higher volumes than 1000

[swarada_jalukar]

Thanks for responding @Nikola Perisic . 

We majorly wanted to know about how much volume is expected in an hour or a day? Eg, 1.5 million records in a day or so? Can you please clear on this point.

[Nikola Perisic]

@swarada_jalukar 

The primary drivers behind the volume of audit events are the number of active users and the intensity of their activities within Jira. Other significant factors include:

• Number of Active Users: An organization with a large user base will naturally generate a higher volume of audit events. As a baseline, an instance with 600 active users can produce approximately 20,000 events daily. For an enterprise with thousands or tens of thousands of users, this number would scale, though not always linearly, as user activity levels can vary.

• Jira Usage and Configuration: The way your organization uses Jira plays a crucial role. Frequent activities that generate a high volume of audit events include:

  • Issue creation, deletion, and updates

  • Workflow transitions

  • Project creation and configuration changes

  • Permission scheme modifications

  • User management activities (adding/removing users, group changes)

• Audit Log Coverage Level: Jira administrators can configure the level of detail captured in the audit logs. There are typically different coverage levels (e.g., Base, Advanced, Full), with each successive level logging more granular events and consequently increasing the data volume.

• Third-Party Applications and Integrations: Marketplace apps and other integrated tools can generate their own audit events. The more applications you have connected to your Jira instance, the higher the potential for increased audit log traffic.

• Automation Rules: The number and complexity of automation rules can significantly impact the volume of audit records. Each time a rule is triggered, it generates an entry in the audit log.

[swarada_jalukar]

@Nikola Perisic , Thank you so much! Got cleared now..

[Nikola Perisic]

@swarada_jalukar kindly accept the answer