# Session History

This feature allows swift identification of resource-intensive sessions/queries, pinpointing slowdown sources, and determining CPU, IO, and other resource consumption.

The dashboard presents data in a multi-dimensional manner, offering options for time selection, time zooming, and tag-based filtering for enhanced visualization and analysis.

{% hint style="info" %}
Session sampling is done every 10 seconds
{% endhint %}

> Automated Tags are generated through the active session sampling process on pg\_stat\_activity

* [wait\_event\_type](/manual/features/tips-and-hints/wait-event-description.md)
* [wait\_event](/manual/features/tips-and-hints/wait-event-description.md)
* application\_name
* client\_host\_name
* command\_type
* query\_md5\_id
* user\_name

{% hint style="info" %}
[Tags](/manual/features/tips-and-hints/tags.md) provide additional context and categorization to the data, allowing for more detailed analysis and insights.
{% endhint %}

{% hint style="info" %}
Within the dashboard, three small charts are prominently displayed, allowing you to select [Cluster or System Metrics](/manual/features/key-features/cluster-and-system-metrics.md) for correlation. Refer to [Metric Correlation](/manual/features/tips-and-hints/metric-correlation.md) section for more details
{% endhint %}

{% content-ref url="/pages/dbLGoTRlMNoFwgFYcbNF" %}
[Metric Correlation](/manual/features/tips-and-hints/metric-correlation.md)
{% endcontent-ref %}

{% hint style="info" %}
For comprehensive insights into wait events and their types, hover over the description tooltips as documented [here](/manual/features/tips-and-hints/wait-event-description.md).
{% endhint %}

## Interactive Demo

{% @arcade/embed flowId="isimuO4HUbeI0q1amrgr" url="<https://app.arcade.software/share/isimuO4HUbeI0q1amrgr>" %}


---

# Agent Instructions: 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:

```
GET https://docs.datasentinel.io/manual/features/key-features/session-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.