⌚Live360

Datasentinel offers a direct connection feature to PostgreSQL instances, enabling real-time retrieval of information.

Live360 exclusively establishes direct connections with PostgreSQL instances, setting it apart as the sole module with this capability.

The remaining analysis dashboards acquire data from the repository. Users of Datasentinel have the flexibility to enable or disable this specific feature on an individual basis.

Refer to Blog Post

Current Sessions

You have the option to select either a specific database or all databases, allowing you to then filter for active sessions and display the associated queries.

From left to right, the above indicators are

Number of active sessions
Number of connected sessions
Database activity graph : Are the sessions on CPU, Waiting, … ?
Number of currently blocked sessions

By simply clicking on a session, you can delve into its details and gain a comprehensive understanding.

Blocking Sessions

The interface displays both blocking and blocked sessions. You can access further session details by clicking on a specific session.

From the interface, you have the capability to terminate sessions directly.

For the ability to terminate a session, the user currently accessing the interface needs to hold the read write or admin privilege, and the monitoring user within the PostgreSQL cluster must be granted the role pg_signal_backend

Relation Statistics Explorer

Opt for your desired database, select the schema, then choose the relation type between

Table
Index
Materialized view
Foreign table
View
Extended Statistics
Extension
Function / Proc
Sequence
TOAT table

Example of displayed elements for a table

Columns statistics
Partitions
Indexes
Constraints
Options
Extended statistics
TOAST

For accessing certain internal statistics (such as pg_statistic_ext and pg_stats), the PostgreSQL user used by Datasentinel must possess specific rights and privileges

// Grant example
GRANT SELECT ON ALL TABLES IN SCHEMA pg_catalog TO datasentinel;

Execution Plans

Select your database and generate an execution plan from any query.

You can choose the ANALYZE option to execute the query in order to have its overall and step by step execution time statistics.

ANALYZE option is only available for SELECT statements.

When choosing ANALYZE, specify a timeout to set the maximum allowed execution time of the query

The execution plan viewer makes it easy and quick to understand each step.

The output can be text or json

In-Progress Operations

Follow the progress of current operations

PostgreSQL Version

Operation

ALL

VACUUM

>= 12

CREATE INDEX

CLUSTER

VACUUM FULL

>=13

ANALYZE

>=14

COPY

Disk Usage

Disk usage lets you explore the space consumed by relations.

You have the option to either observe the space usage for individual databases or for all of them.

Result can be grouped based on:

relations
schemas
tablespaces

Cache Usage

Cache usage lets you explore the space consumed by relations in memory (shared_buffers)

For utilizing this functionality, it's necessary to install the pg_buffercache extension across all databases within your instance.

You have the option to either observe the space usage for individual databases or for all of them.

PreviousCluster & System Metrics NextReporting

Last updated 1 year ago