> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/soda-documentation/data-observability/metric-monitoring-dashboard/column-monitors/numeric/q1.md).

# Q1

{% hint style="warning" %}
This metric is not supported in MySQL.
{% endhint %}

### Definition

Quartiles divide all non-NULL values in the column within the latest partition into four equal parts based on value: Q1 represents the 25th percentile.

### Source

data (numeric)

### Computation

* For data sources supporting exact percentiles (e.g. PostgreSQL’s `PERCENTILE_DISC(0.25)`), Soda uses that function.
* For data sources that provide approximations (such as BigQuery, SQLServer, Redshift and Trino), Soda uses those approximated values.

<br>

***

{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/soda-documentation/reference/documentation-access-and-licensing.md).
{% 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.soda.io/soda-documentation/data-observability/metric-monitoring-dashboard/column-monitors/numeric/q1.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.