> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2025/2025-08-08-cop-statistics.md).

# 2025-08-08: COP - Tenant Usage Statistics

## Overview

We are announcing a significant enhancement to the Management Dashboard — Tenant Usage Analytics — which will empower tenant administrators with comprehensive visibility into resource consumption and system usage per tenant.

## New features

| Feature                                                 | Benefit                                                                                                                                                               |
| ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Aggregated API usage metrics (total & per endpoint)** | Enables administrators to monitor API consumption patterns and identify high-traffic endpoints, supporting scaling and optimization decisions.                        |
| **Webhook events tracking**                             | Provides transparency on triggered webhook events, assisting with event-driven system integrations and usage analysis.                                                |
| **Storage consumption**                                 | Gives insights into current storage usage and growth over time.                                                                                                       |
| **AI tokens consumption**                               | Offers visibility into AI resource usage, helping manage consumption and predict token requirements for future usage.                                                 |
| **Selectable time periods (daily, weekly, monthly)**    | Allows flexible analysis of trends over customizable timeframes, facilitating detailed usage monitoring and reporting.                                                |
| **Visualized statistics through charts & tables**       | Presents data in clear, actionable formats, making it easier to interpret.                                                                                            |
| **Multiple tenant selection**                           | Simplifies the overview of all tenants assigned to a user, enabling quick switching and consolidated monitoring for multi-tenant administrators.                      |
| **CSV download all selected tenants and per tenant**    | Allows exporting usage data in CSV format, either aggregated for all selected tenants or individually per tenant, supporting detailed reporting and offline analysis. |

## Fixes and improvements

None as this is a new feature.

## Known problems

No known problems at time of release.

## Documentation and links

* [Statistics](/user-guides/management-dashboard/administration/consumption-statistics.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://developer.emporix.io/release-notes/archive/2025/2025-08-08-cop-statistics.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.