Has anyone else noticed AI usage killing your Jira instances?

[Jeramy]

Our CEO recently told everyone that they must use Claude to do their Jira work. As of now, we have 150+ PATs all being used for Claude AI agents. Well, my Jira instance crashed this morning and that's the only thing I can think was the reason. 

I'm not sure what to do to prevent AI agents from killing the instance. We are running Jira DC, version 10.3.7. Both of our VMs that host Jira only have 32 GB of RAM in them and they both have mid-range (but older - like 8 years) CPUs. 

How do I limit the amount of incoming API calls, so AI doesn't kill Jira?

[Adrian Woods]

Your thinking is absolutely correct - that's a lot of PATs!

The fastest path to stability is likely to enable built-in rate limiting now → add a reverse proxy with connection limits → plan a hardware upgrade into the future, though I understand that may not be something you're in control of for now. The consolidation of PATs through a gateway is the right long-term architecture here!

Just in case it's not already in place, I let Rovo clean up some instruction for me on how to take a peek at rate limits in case the org is not utilizing them already. See below and wishing you the best of luck here!

Jira DC has native rate limiting available. Go to Administration → System → Rate limiting and configure it:

• Enable rate limiting for REST API requests
• Set a max requests per user per interval — for 150+ AI agents, something like 30–50 requests per user per minute is a reasonable starting point
• You can choose to either block requests that exceed the limit or delay them
• Importantly, rate limiting in Jira DC applies per authenticated user (per PAT), so each of those 150+ PATs gets its own quota

[Martin Runge]

Hi @Jeramy

Have you checked your logs to see if your DC Jira encountered an out-of-memory error?
You could also adjust the JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY if there is free RAM on your VMs. This way, you are not forced to limit the APIs too much.