Issue Summary

With the implementation of rate-limiting in Jira Cloud, more and more customers are running into their cost budgets and 429 errors.

It would be great if there was some visibility (through a report, for instance) into which parts of a Jira instance are consuming the most resources (JQL queries, boards, dashboards, automation rules, add-ons...) so that optimization opportunities can be identified and worked on.

The current situation is that customers run into 429 errors and can't even figure out why.