The Overview page is your starting point for monitoring the operational health of your Jira Cloud instance.

It combines API rate limit monitoring with Jira configuration governance into a single dashboard, allowing administrators to quickly determine whether their site is operating within Atlassian's recommended limits.

This page is designed to answer three important questions:

• Is my Jira instance healthy?

• Do I need to take any action today?

• If something needs attention, where should I investigate?

For most administrators, this should be the first page they review each day.

Understanding the Overview Dashboard

The Overview page is divided into two sections:

• API Rate Limiting – Shows the health of your Jira Cloud API usage.

• Data Limits & Governance – Shows how your Jira configuration compares with Atlassian's recommended platform limits.

The top section helps you monitor short-term operational health.

The bottom section helps you monitor long-term platform scalability.

Open

API Rate Limiting

This section provides a real-time summary of your site's API consumption.

Every request made to Jira Cloud, whether from Marketplace apps, automation rules, integrations, or users, contributes towards Atlassian's API limits.

QuotaWatch continuously monitors these limits and presents the current health of your environment.

API Health Status

At the top of the dashboard you'll see the overall API health indicator.

Possible statuses include:

If the status is Healthy, no action is required.

If the status changes to Degraded or Critical, review the API Activity page to identify the largest consumers.

Hourly API Quota

The Hourly API Quota card shows how much of the current hourly API capacity has been consumed.

This is the primary indicator used to determine whether your Marketplace apps, integrations and automation rules are operating safely.

Healthy

API usage is comfortably below Atlassian's reporting threshold.

No action is required.

Degraded

API usage is increasing.

Large imports, scheduled automation or integrations may be contributing to higher API activity.

Continue monitoring the environment.

Critical

API usage is approaching the available hourly quota.

If the quota is exhausted, API requests may begin to fail until the next reset window.

Investigate high API consumers as soon as possible.

Burst Capacity

Hourly usage is only one part of API monitoring.

Burst Capacity measures how many requests are being sent within a very short period.

Even if hourly usage is low, sending too many requests simultaneously can temporarily trigger Atlassian's protection mechanisms.

A healthy burst capacity means requests are evenly distributed across time.

If burst capacity becomes unhealthy, review integrations or automation rules that generate large numbers of requests at once.

Daily Summary

Several summary cards provide a quick snapshot of API behaviour during the previous 24 hours.

Average Usage

Shows the average API utilization across the last 24 hours.

Consistently high averages usually indicate continuous background activity rather than isolated spikes.

Peak Usage

Shows the highest API utilization recorded during the last 24 hours.

A single peak is not always a concern.

Repeated peaks usually indicate recurring workloads such as scheduled automation or integrations.

Incidents

Displays the number of monitoring periods where API usage exceeded your configured alert thresholds.

An increasing incident count indicates your Jira site regularly operates near its API limits.

Next Reset

Shows the remaining time before Atlassian resets the current hourly API quota window.

Once the quota resets, API capacity becomes available again.

24-Hour Timeline

The timeline provides a visual history of your API health over the last 24 hours.

Each marker represents a monitoring snapshot.

Typical colours indicate:

Use this timeline to identify recurring traffic patterns throughout the day.

For example:

• Daily automation jobs

• Scheduled imports

• Bulk issue updates

• Third-party integrations

Recurring spikes often indicate opportunities for optimisation.

Data Limits & Governance

The second half of the Overview page focuses on the overall health of your Jira configuration.

While API monitoring helps you understand current operational health, governance monitoring helps ensure your Jira site remains scalable as it grows.

QuotaWatch compares key Jira configuration objects against Atlassian's recommended limits and summarizes the overall health of your site.

Governance Score

The Governance Score provides an overall indication of how closely your Jira configuration aligns with Atlassian's recommended platform limits.

A higher score means your Jira site has comfortable capacity for future growth.

A lower score indicates one or more areas should be reviewed before they become operational concerns.

The score is intended to help prioritise maintenance activities rather than replace detailed investigation.

Space-Level Guardrails

This section monitors limits that apply to individual Jira projects; and will show how many guardrails are crossing the space level threshold limit set by user / how many guardrails crossing the space level critical threshold.

Typical examples include:

• Custom Fields

• Components

• Releases

• Work Types

Projects approaching recommended limits should be reviewed before additional configuration is added.

Site-Wide Guardrails

This section summarises configuration shared across the entire Jira site, and will show how many guardrails are crossing the threshold limit set by user / how many guardrails crossing the critical threshold.

Examples include:

• Projects

• Issues

• Workflows

• Statuses

• Priorities

• Security Levels

• Permission Grants

These metrics help administrators understand whether the Jira instance is growing sustainably.

Recommendations

If QuotaWatch identifies opportunities for improvement, recommendation cards appear below the dashboard.

Examples include:

• Projects with no active issues

• Configuration objects approaching recommended limits

• Areas where cleanup may improve long-term maintainability

Each recommendation explains what was detected, why it matters, and what action is recommended.

Frequently Asked Questions

Why does API usage sometimes show less than 80%?

Atlassian only provides detailed API rate limit information after usage reaches its reporting threshold. When usage remains below that threshold, QuotaWatch indicates that the environment is operating normally.

Does a high peak always indicate a problem?

No.

Temporary increases during imports, migrations or scheduled automation are expected.

Only repeated or sustained peaks generally require investigation.

Does a high Governance Score guarantee good Jira performance?

No.

The Governance Score measures how closely your Jira configuration aligns with Atlassian's recommended limits.

Application performance can also be affected by workflows, Marketplace apps, indexing, automation rules and other operational factors.

Where should I go if I see a warning?

If the warning relates to API usage, open the API Activity page to identify the largest consumers.

If the warning relates to Jira configuration growth, open Data Limits Governance to review the affected areas and recommended actions.

Related Pages

Continue with the following pages to investigate your Jira environment in more detail:

• QuotaWatch for Jira : API Activity

• Data Limits Governance – Monitor Jira configuration growth and platform limits.

• History – Review historical API usage and incidents.

• Settings – Configure monitoring preferences and alert notifications.