> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/kb/backoffice-features/tbd.md).

# Insights

"Insights" help you access a high-level report on the monthly usage of your Appmixer instance: number of messages and message size. This view helps you see the performance of your Appmixer instance over time.

![Backoffice – overview](https://660555879-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Meyy9fJyhzsrd3q4-5N%2F-MhYkD1RwZckVa0ICxQp%2F-MhYkqmvuDtLWiW3-Maa%2FScreen%20Shot%202021-08-20%20at%2015.32.27.png?alt=media\&token=d77cedf8-bc98-4fcb-a65c-1a98b0a62b32)

{% hint style="info" %}
Note that you can view the report for the past 6 months only.
{% endhint %}

As you can see above, our Appmixer instance sends around 50 000 messages a month where one message has 230 bytes on average.

Let's clarify what a message means. The best explanation would be: "information in the JSON Object format that is sent from the *out port* to the *in port* in an Appmixer flow". The size of the message, of course, depends on the data size you're sending from one component to another.

[Next, we'll look at the "Flows" tab – a place where you can access all flows created in your Appmixer instance](/kb/backoffice-features/flows.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.appmixer.com/kb/backoffice-features/tbd.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.