I’m working on upgrading our jira integration in our own product so it can connect to a Cloud-based Jira tenant. I got the connection working, but as shown in multiple posts on here, Jira Cloud has API rate limiting on a tenant level. Problem is, I’m trying to trigger this rate limiting in our testing cloud environment, but it seems to be a much higher rate limit than I can feasibly reach with a single thread doing serial API requests to read issues or add comments to issues.
The only actions we do repetitively is reading half a dozen fields from issues one at a time based on commit messages, and adding comments to these issues once we’ve read all the information. we also have something that reads out server info, but that’s only to test the connection. In our own production environment with an on-premise jira, we have had times when we read out and created comments on over 200 issues.
I was able to add almost 1500 comments in about 10 minutes without getting 429 warnings. And weirdly enough, the X-RateLimit headers and retry-after headers that I’m supposed to use to monitor my usage do not seem to be added as HTTP headers to my REST API calls at all.
I’d normally try this on our local test JIRA server, but it’s a Jira Server, not a Jira Data Center install, so I can’t configure rate limiting at all.
How can I test whether my cloud integration handles rate limiting properly? As it stands I’m not even getting the headers that are informing me about the usage, so I’m not quite sure how to proceed.