> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/intelligence/statistics/frequency-distribution.md).
# Frequency Distribution
Frequency Distribution shows how often each unique value appears within the selected audit logs.
It groups audit logs by the selected field and counts the number of occurrences for each value, making it easy to understand the composition of your data and identify the most and least frequent values.
Examples:
* Distribution of HTTP status codes
* Distribution of customer segments
* Distribution of decision outcomes
* Distribution of rule aliases
* Distribution of users or API keys
This visualization is useful for:
* Identifying the most common values
* Detecting outliers or unexpected values
* Understanding the overall composition of audit data
* Comparing how values are distributed across different datasets or time periods
{% hint style="info" %}
**Visualization Limitation**
When more than **10,000** audit logs match the selected filters, statistics are calculated from a sampled subset of records to maintain performance. The sample is intended to be representative but may not perfectly reflect the full dataset.
{% endhint %}
{% hint style="info" %}
**Export Limitation**
Exports use the same sampled dataset as the visualization, so exported results reflect the same limitation of **10,000**.
{% 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.decisionrules.io/doc/intelligence/statistics/frequency-distribution.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.
