# Wait Event Description

It represents a situation where a process is pausing its operation, waiting for a certain condition to be met or a resource to become available.

### Wait Events

By analyzing these wait events, users can identify what resources or conditions are causing delays.

In the [Session History](/manual/features/key-features/session-history.md) dashboard, located in the bottom left, you'll find an option that allows you to group the workload by wait events.

Accompanying each wait event is a question mark icon, which, when hovered over, reveals a description of the event.

Given the extensive variety of wait events in PostgreSQL, as detailed in the [PostgreSQL documentation](https://www.postgresql.org/docs/current/monitoring-stats.html#WAIT-EVENT-ACTIVITY-TABLE), merely knowing the event's name may not suffice for a comprehensive understanding of what happened.

{% hint style="info" %}
This is where the tooltip feature, offering a full description of each event, becomes immensely beneficial.
{% endhint %}

<figure><img src="/files/m9AT1dZu4UiGwd6TvLsj" alt=""><figcaption></figcaption></figure>

### Wait Event Types

PostgreSQL categorizes wait events into various types, such as I/O waits, lock waits, network waits, and more.

A **wait event type** refers to a specific category under which various wait events are classified. These types represent different kinds of operations or resources that a database process may need to wait for during its execution.

<figure><img src="/files/zzo4wOJcWuOUMxTvN0UC" alt=""><figcaption><p>Session History Dashboard Displaying Workload Grouped by Wait Event Types</p></figcaption></figure>

{% hint style="info" %}
In the [Session History](/manual/features/key-features/session-history.md) dashboard, you have the flexibility to organize the workload either by wait event types or specific wait events.

This grouping can be applied both within the timeline chart and/or in the bottom left section of the dashboard, offering a comprehensive view of your database's performance dynamics.
{% endhint %}


---

# 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/tips-and-hints/wait-event-description.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.