> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/generate-reports/custom-reports/add-a-metric-card-number-chart.md). # Add a Number Chart Use a **Metric Card** (called **Number Chart** in the UI) to display a single aggregated value, such as the number of issues, applications, or resolved items in a defined time range. Metric Cards are useful for highlighting KPIs and high-level counters in a custom report.
| Area | Description | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | Widget name | The name of the widget appears as the title on the report tile. | | Data source | Dataset used to calculate the value, such as Issues, SBOM, Applications, Pipeline Issues, Resolved Issues, or Removed Issues. | | Date range |

Time window for the calculation.
Available for the following data sources:
- Pipeline Issues
- Resolved Issues
- Removed Issues

| | Filters | Widget-level filters that limit which items are counted. These filters apply only to this widget and are saved with it. | | Preview | Live preview of the calculated value based on the current configuration. | **To add a Metric Card:** 1. In **Custom Reports**, select **ADD WIDGET > Number Chart**. 2. In **Widget name**, enter a clear title that reflects both the metric and the time window, for example, *Resolved issues – last 90 days*. 3. In the **Data source**, select the dataset to count. 4. If available for the selected source, configure the **Date range**. > **Note:**\ > The global date range overrides the widget’s saved date range. When no global date range is selected, the widget uses its own configuration. 5. Open **Filters** and apply any widget-level filters needed to narrow the count. 6. Review the **Preview** to confirm the value. 7. Select **SAVE WIDGET**. --- # 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.ox.security/generate-reports/custom-reports/add-a-metric-card-number-chart.md?ask=&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.