View app usage in Confluence Data Center
App Usage helps Confluence administrators understand how installed Marketplace apps are used in their site. It provides visibility into app REST API activity, Active Objects database tables, and macro usage so administrators can assess app adoption, identify content dependencies, and make more informed decisions about upgrades, migrations, and app lifecycle management.
Available in: Confluence Data Center 10.2.11 and 9.2.20, and later patch releases.
Before you begin
You must be a Confluence administrator to access App Usage.
Open App Usage
Go to Administration > Atlassian Marketplace.
Select App Usage.
Choose an installed app to view its usage details.
The Common Usage Data tab can include the following sections:
REST API usage
Database tables
Macro usage
Understand REST API usage
The REST API usage section shows calls made to REST APIs provided by an app.
When an app implements the REST plugin module, App Usage displays calls made through that module. Calls that do not go through the app's REST plugin module, such as external calls, are not tracked in this view.
If an API path changes, App Usage shows the latest path and combines usage data collected from both the old and new paths. Usage data is refreshed every five minutes.
Tracking starts only after App Usage is enabled. It does not include historical REST API activity from before the feature was enabled.
The following table explains the information shown in this section.
| Column | Description |
|---|---|
| X REST API calls made by X users | The total number of REST API calls made since tracking began, and the number of users who made those calls. |
| User | A user who interacted with the app's REST API, either directly or indirectly. |
| Call count | The number of times that user made that specific API call. |
| Last used | The most recent time that user made that specific API call. |
Understand database tables
The database tables section shows the tables introduced by an app and a snapshot of their current row counts.
App Usage shows tables implemented through the Active Objects framework only. If an app uses tables it did not define through Active Objects, or uses a different persistence mechanism, those tables are not shown.
The following table explains the information shown in this section.
| Column | Description |
|---|---|
| X database tables | The total number of database tables introduced by the app. |
| Table | The name of the database table. |
| Row count | The current number of rows in the table. Updates to row counts may take some time to appear. |
Understand macro usage
The macro usage section shows which app-provided macros are embedded in Confluence content.
This section uses Confluence search to identify pages that contain app-specific macros. It helps administrators understand content-level app dependencies, estimate the impact of removing or replacing an app, and identify macros that are widely used across the site.
The following table explains the information shown in this section.
| Column | Description |
|---|---|
| Macro name | The name of the macro provided by the app. |
| Last modified | The most recent time a page containing this macro was modified. |
| Page count | The number of unique pages in the site that contain this macro. |
Disable App Usage or usage tracking
You can use feature flags to disable the App Usage menu or specific usage data.
Feature flag | Description |
|---|---|
app.usage.menu.disabled | Disables or re-enables the App Usage menu in the administration interface. |
plugin.app.usage.common-usage-data | Disables or re-enables Common Usage Data, including REST API usage and database tables. |
| plugin.app.usage.macro-usage-views | Disables or re-enables macro usage data. |