Uploaded image for project: 'Opsgenie'
  1. Opsgenie
  2. OPSGENIE-2087

Have the ability to drill down to see to see API usage per second/minute and response codes

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User Issue:

      Currently, the API usage Analytics report just gives you a high-level overview of the API usage and there isn't an option available to look into the usage in detail. For example:

      • per minute/second usage
      • response codes (with option to see endpoints for each) 

      Suggestion:

      It would be great to see the usage in detail so admins can keep track of the API usage and take necessary actions if the rate limit is being reached.

      Workaround:

      N/A

            [OPSGENIE-2087] Have the ability to drill down to see to see API usage per second/minute and response codes

            In addition to the per-minute/second usage, I'd also like to see whether requests were throttled or not. Currently we ask Atlassian support to manually share CSVs with detailed request data but ideally the dashboard can  answer the same questions without manual CSV export.

            Lastly the dashboard is also really slow, would appreciate if the performance can be improved.

            Prashanth Chandra added a comment - In addition to the per-minute/second usage, I'd also like to see whether requests were throttled or not. Currently we ask Atlassian support to manually share CSVs with detailed request data but ideally the dashboard can  answer the same questions without manual CSV export. Lastly the dashboard is also really slow, would appreciate if the performance can be improved.

            +1

            garvit.jain added a comment - +1

              Unassigned Unassigned
              ad7c4ffcfed3 Sean Suwal
              Votes:
              7 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: