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

# Kangal Analytics

Kangal Analytics is a built-in snapshot of tenant telemetry already recorded by Kangal.

## What sync does

The sync reads one document from the `gateway_metrics` collection whose `tenant_id` matches the current tenant. From that document it reads `updated_at`, `rate_limit_hits_7d`, `route_latency`, and `plugin_latency`.

If no matching document exists, the sync still succeeds and returns `message: "No metrics recorded for tenant."`.

## Required values

This built-in integration requires no configuration or credentials.

## Metadata returned

| Field                | Meaning                                                        |
| -------------------- | -------------------------------------------------------------- |
| `last_updated_at`    | Stored metrics document timestamp                              |
| `rate_limit_hits_7d` | Stored seven-day rate-limit counter, defaulting to `0`         |
| `route_count`        | Number of keys in the document's `route_latency` object        |
| `plugin_metrics`     | Plugin names present in the document's `plugin_latency` object |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kangal.dev/integrations/kangal-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.