Datasentinel Docs
Visit our websiteBlogRelease Notes
  • 👋Welcome
  • 🆓Free Trial
  • 📣Release Notes
  • Getting started
    • Architecture
    • Installation
      • 🌐Platform
      • 🕶️Agent
    • PostgreSQL clusters
      • 🔌Extensions
        • 🔌pg_stat_statements
        • 🔌pg_store_plans
        • 🔌system_stats
        • 🔌pg_buffercache
      • 🕶️Monitoring User
      • ➕Adding Connection
    • FAQs
      • ❓Platform FAQ
      • ❓Agent FAQ
  • Features
    • Key Features
      • 📊Session History
      • 📊Top Queries
      • 📂Top Tables
      • 🔓Lock Explorer
      • 📈Cluster & System Metrics
      • ⌚Live360
      • 📰Reporting
      • 🔔Alerting
        • Settings
        • Templates
        • Silences
        • Manager
    • Other Features
      • 📡Agentless Monitoring
      • 🛡️Role Based Access
      • 🔂Changed Parameters
    • Tips & Hints
      • 🖥️User Interface
      • 🏷️Tags
      • 🔀Metric Correlation
      • 👁️‍🗨️Consolidated View
      • ❗Graphical Annotations
      • ☁️Predefined Providers
      • ❓Wait Event Description
      • ®️Read Replicas
      • 👁️‍🗨️Agentless & System Metrics
      • ☑️Simplified pg_instance Display
  • implementation
    • Platform Usage
      • ⚙️Configuration
        • 🔑License
        • 📓LDAP
        • ✉️SMTP
        • 📋Audit
        • 👨‍🏭Users & Roles
      • 🧩API
        • 🔗Access Token
        • 🧩Connection API
        • 🧩Role API
        • 🧩User API
        • 🧩Reporting API
        • 🧩Workload API
        • 🧩Alerting API
      • 🛠️Tooling
    • Agent Usage
      • 📣Release Notes
      • ⌨️CLI
      • 🧩API
      • 🗃️Collection Level
      • 🔬Internals
    • Upgrade
      • 🔄Platform
      • 🔄Agent
    • Troubleshooting
      • 🩺Error message: “502 Bad Gateway”
      • 🩺The UI is not displaying any metrics for my new instance.
      • 🩺UI dashboard is encountering loading errors
      • 🩺InfluxDB
  • Support
    • How to Contact Us
  • GitHub Toolkit
Powered by GitBook
On this page
  • Wait Events
  • Wait Event Types
  1. Features
  2. Tips & Hints

Wait Event Description

A wait event in PostgreSQL is a fundamental concept used in performance monitoring and tuning.

PreviousPredefined ProvidersNextRead Replicas

Last updated 1 year ago

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 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 , merely knowing the event's name may not suffice for a comprehensive understanding of what happened.

This is where the tooltip feature, offering a full description of each event, becomes immensely beneficial.

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.

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.

In the dashboard, you have the flexibility to organize the workload either by wait event types or specific wait events.

❓
Session History
Session History
PostgreSQL documentation
Session History Dashboard Displaying Workload Grouped by Wait Event Types