Version 2026.05 has been released
Ctrlk
WebsiteAPI ReferenceChangelog
For the complete documentation index, see llms.txt. This page is also available as Markdown.
RSS feed

2025

Datasentinel releases from 2025.

FeatureImprovementFixesChanges

V2025.11

PostgreSQL 18

Fully compatible with the latest PostgreSQL 18 release

Limit configuration for Agentless connections

When connecting to PostgreSQL clusters using the Agentless method, you can now define limits for the maximum number of monitored tables and queries per cluster. This capability was previously available only for clusters monitored by local agents.

Refer to Agentless Monitoring section for more details

Messaging

To enhance clarity, intrusive "no data found" messages have been removed or improved:

  • In the Active Session History chart, the message now appears as a subtle header note: &#xNAN;"No active sessions detected" when no metrics are available.

  • In the Top Queries dashboard, the message has been updated to: &#xNAN;"No metrics available for the selected time range", providing clearer context for users.

Diagnostic Scripts

Two diagnostic scripts have been added to help identify and troubleshoot platform issues more efficiently. For details, see the Diagnostic Tools section of the documentation.

Libraries

Updated third-party libraries for better performance, security, and compatibility

API

A new column has been added to the response of the Instance Information API

  • "last_collection_time": Timestamp of the most recent data collection for this instance.

Agent v3.8.0

Refer to the Agent Release Notes

🔧 Fixes

  • Solaris Compatibility for system_stats extension Resolved an issue where the system_stats extension running on Solaris systems was missing certain metric fields. The Agentless feature now embeds the updated agent version to ensure complete and accurate metric collection.

  • Reliable Patch Application The patch script now writes its log file to /tmp instead of the current directory. This prevents failures when the user lacks write permissions, ensuring backend and dispatcher services restart properly with the new binaries.

  • Faster Instance Deletion When deleting an instance from Datasentinel UI, only the most recent status metrics are now removed instead of the entire history. This speeds up the deletion process.

  • Deduplication Resolved an issue where recent changes to tags caused duplicate instance entries in Instance Information API. Duplicates are now automatically removed by keeping only the most recent last_collection_time.

Fixes

V2025.07

🔧 Fixes

LDAP user updates Editing an LDAP-authenticated account no longer clears its “LDAP” flag; the user now retains that status and remains visible in the Users dashboard after an update.

ImprovementFixesChanges

V2025.06

API

New columns have been added to the response of the Instance Information API

  • "type": The instance type — either "primary" or "replica".

  • "port": The listening port of the instance (requires Agent version 3.7+ if using local agents).

  • "databases": Total number of databases in the instance.

  • "size": Total size of the cluster in bytes.

Agent v3.7.0

Refer to the Agent Release Notes

🔧 Fixes

  • In rare cases, the log file backend_to_influx.log related to InfluxDB write errors could grow excessively large. Its size is now limited to 256 MB, with a maximum of one backup file. Refer to the Log Files section.

  • Resolved an issue with dynamic filters on the dashboard that affected the display of registered users.

FeatureImprovementChanges

V2025.02

FUJITSU Enterprise Postgres

We have updated the Fujitsu logo in our software to comply with their brand usage guidelines.

Datasentinel is now officially integrated with Fujitsu Enterprise Postgres 17 SP1. This ensures seamless compatibility and monitoring support for users running Fujitsu’s enterprise-grade PostgreSQL solution.