Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-45489

As an admin, I would like the ability to limit API Connections

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • 11
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Excessive logins can eventually compete with Apaches ability to maintain open database connections.

      Looking at our API docs:
      https://developer.atlassian.com/display/HOME/Atlassian+REST+API+policy#AtlassianRESTAPIpolicy-Resource/ratelimitsandpaging

      We state:

      Resource/rate limits and paging

      Resource and rate limits, and the default and maximum sizes of paged data ARE NOT considered part of the API and may change (possibly dynamically). It is the responsibility of the client to read the road signs and obey the speed limit.

      For Cloud users, excessive logins aren't visible to the admins. That being said, ideally we could allow admins the ability to define a max concurrent connection on a per account basis and/or a way to throttle inbound API calls to the Cloud instance (for example, keep the traffic from hitting 300 on an hourly basis, etc).

      We're seeing cases where logins are nearly reaching the 500K mark, mainly service accounts logging in via the API.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jworley Jason Worley (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: