> For the complete documentation index, see [llms.txt](https://docs.upriverdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.upriverdata.com/product-usage/data-assets/pivot-fields.md).

# Pivot Fields

## Overview

In order to gain a more granular sub-profile of the data, the platform let’s you define pivot fields. These allow you to monitor subsets of the data independently by specifying the field which serves as a “pivot” for your data.

<figure><img src="https://875415170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLE0zsJmUpeLjYw085cnO%2Fuploads%2FruM3YmSCpNozZKjaZoeR%2Fimage.png?alt=media&amp;token=ae27d4e7-0ca1-47c5-9987-cb0d00b15a20" alt=""><figcaption><p>Catalog overview with pivot fields defined for two data sources.</p></figcaption></figure>

## Derived data sources

For each pivot field defined, Upriver automatically generates a “derived data source” for every unique value within that field, enabling all of Upriver’s monitoring capabilities on each sub-profile. This setup allows users to independently monitor and analyze trends specific to each pivot value, providing more granular insights into their data. Users only need to define the pivot field itself—Upriver handles the creation and tracking of all derived data sources automatically.

In cases where multiple pivot fields are defined, Upriver generates and monitors all possible combinations of pivot values, ensuring comprehensive monitoring of every data variation without requiring any additional setup.

{% hint style="info" %}
Even when pivots are defined, the "parent" data source which defines the pivot is still monitored independently in order to give a full overview of the data source.
{% endhint %}

### Relation to parent data source

#### Configuration

Derived data sources are monitored at the same time as the parent data source which creates the pivot. When performing configuration on a parent data source, there is an option to apply the configuration to all of the derived data sources as well. For example, when changing the sampling rate, the user will be prompted whether they want to apply the change to all the derived data sources in addition to the parent.

<figure><img src="https://875415170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLE0zsJmUpeLjYw085cnO%2Fuploads%2FHiBPxUGFamgc1jxR8X4q%2Fimage.png?alt=media&amp;token=11a15c18-8745-4b24-9d47-00664c1d2ecc" alt="" width="375"><figcaption><p>Prompt regarding derived data sources when updating the<br>configuration of a data source with pivots</p></figcaption></figure>

#### Incidents

When incidents are detected for derived data sources, Upriver checks if the incident also appears in other derived data sources for the same parent and also in the parent data source. If this is the case, Upriver groups these incidents in order to not flood users with multiple incidents which are the same. Otherwise, incidents for derived data sources are shown independently as with all other data source.