I have a VMWare admin who's using a monitoring system to open JIRA tickets with a dedicated user account and using the API to do so. We were wondering if there's a way to limit the number of concurrent API calls in casea major VMWare event tries to open a large number of tickets causing performance problems.
I'm not seeing anything in the UI or any documentation for editing a conf file or Database. Any ideas? Am I missing it? Can someone point me in the right direction?
Thanks!
--Eric
Thanks for the quick response. We've tested this on a non-prod system and it is working fine and there is no current "large ticket" issue. We're trying to protect against a possible future event by setting the API limit. We had a VMWare problem last fall and (though it shouldn't happen again) it is on the checklist of things to try to protect ourselves from.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We can put in a "feature request" like this in support.atlassian.com. They will usually respond if it's feasible or not right away :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.