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

# Insights

Dashboards and logs of your Sendman instance

The **Insights** menu group contains dashboards that show what happens on your Sendman instance:

* [Overview](/admin-portal/insights/overview.md): key figures on connections and delivered messages
* [Logs](/admin-portal/insights/logs.md): the detailed log of every connection and message
* [Uptime](/admin-portal/insights/uptime.md): the availability of your instance

All dashboards share the same controls:

* **Search bar:** filter the data with a query, e.g. a sender address or a client IP address.
* **Time filter:** choose the period to display. The default is the last 15 minutes.
* **Open in new tab:** the icon next to the page title opens the dashboard in a separate browser tab with more space.

{% hint style="info" %}
Logs never contain passwords or other credentials.
{% endhint %}


---

# 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.sendman.com/admin-portal/insights.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.