> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/insights/usage.md).

# Usage

The Usage tab gives you an overview of how the components in your apps are used. For modules, it shows how often your app uses the elements they provide, such as Java actions, microflows and entities. For widgets, it shows how often they are used on pages. These usage records show which parts of a component your app depends on, which helps you plan upgrades and maintain your apps.

The usage data is generated every time an app model is processed, so it always reflects the most recently processed revision. It is also used to estimate the effort needed to upgrade components, for example by the policy check [COMP\_0014 - Component upgrade effort](https://docs.bluestorm.io/checks/component/comp_0014.md).

Each row shows one component used by one revision of an app.

### Filters

You can filter the list on the following columns:

* App. The name of the app.
* Revision. The revision of the app.
* Component type. The type of component.
* Component name. The name of the component.
* Count usage. The total number of usages. Use this to find components that are used more or less often.

### Columns

Some columns are hidden by default. To show or hide columns, use the column selector at the top right of the grid. Unhide the columns you need before downloading the overview.

| Column                    | Shown by default | Description                                                                                                                                                                                                                                                          |
| ------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| App                       | Yes              | The app that uses the component.                                                                                                                                                                                                                                     |
| Revision                  | Yes              | The revision of the app that was processed.                                                                                                                                                                                                                          |
| Component type            | Yes              | The type of component, for example a module or widget.                                                                                                                                                                                                               |
| Component GUID            | No               | The unique identifier of the component.                                                                                                                                                                                                                              |
| Component name            | Yes              | The name of the component.                                                                                                                                                                                                                                           |
| Version                   | Yes              | The version of the component that is used in the app.                                                                                                                                                                                                                |
| Target                    | Yes              | The version that the upgrade effort is calculated for. If this is the same as the current version, the component is up to date and no effort is needed.                                                                                                              |
| Count usage               | Yes              | The total number of times the component is used in the app.                                                                                                                                                                                                          |
| Count actions             | No               | The number of microflow, nanoflow and rule actions that use the component.                                                                                                                                                                                           |
| Count pages               | No               | The number of widget placements on pages that use the component.                                                                                                                                                                                                     |
| Count java actions        | No               | The number of Java actions that use the component.                                                                                                                                                                                                                   |
| Count entity associations | No               | The number of associations that use an entity of the component.                                                                                                                                                                                                      |
| Count Entity Inheritance  | No               | The number of entities that inherit from an entity of the component.                                                                                                                                                                                                 |
| Count entity page         | No               | The number of usages of an entity of the component on pages.                                                                                                                                                                                                         |
| Count entity microflow    | No               | The number of Create and Change usages of an entity of the component in microflows.                                                                                                                                                                                  |
| Upgrade Priority          | Yes              | A score that ranks components by how urgently they need attention. It combines the upgrade effort with an urgency weight based on the support status of the component and how many versions it is behind. A higher score means the component needs attention sooner. |
| Upgrade Effort            | Yes              | The estimated effort to upgrade or replace the component to the target version. The value is calculated with the options of the policy check COMP\_0014 - Component upgrade effort.                                                                                  |

### Related

* [COMP\_0014 - Component upgrade effort](https://docs.bluestorm.io/checks/component/comp_0014.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluestorm.io/dashboards/insights/usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
