# 2025

{% updates format="full" %}
{% update date="2025-11-12" tags="feature,improvement,fix,changes,fixes" %}

## V2025.11

### PostgreSQL 18

> Fully compatible with the [latest PostgreSQL 18 release](https://www.postgresql.org/docs/18/index.html)

### 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](/manual/implementation/agent-usage/cli.md#change-table-monitoring-limit).
>
> Refer to [Agentless Monitoring](/manual/features/other-features/agentless-monitoring.md) section for more details

### Messaging

> To enhance clarity, intrusive **"no data found"** messages have been removed or improved:
>
> * In the [**Active Session History**](/manual/features/key-features/session-history.md) chart, the message now appears as a subtle header note:\
>   \&#xNAN;**"No active sessions detected"** when no metrics are available.
> * In the [**Top Queries**](/manual/features/key-features/top-queries.md) 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**](/manual/implementation/troubleshooting/platform-diagnostics-tools.md) 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**](/manual/implementation/platform-usage/api-reference/workload.md#informations)
>
> * "**last\_collection\_time**": Timestamp of the most recent data collection for this instance.

### Agent v3.8.0

> Refer to the [Agent Release Notes](/manual/implementation/agent-usage/release-notes.md)

#### :wrench: Fixes

> * **Solaris Compatibility for `system_stats` extension**\
>   Resolved an issue where the [system\_stats](https://github.com/EnterpriseDB/system_stats) extension running on Solaris systems was missing certain metric fields.\
>   The [Agentless feature](/manual/features/other-features/agentless-monitoring.md) 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**](/manual/implementation/platform-usage/api-reference/workload.md#informations). Duplicates are now automatically removed by keeping only the most recent `last_collection_time`.
>   {% endupdate %}

{% update date="2025-07-21" tags="fix,fixes" %}

## V2025.07

### :wrench: Fixes

> **LDAP user updates**\
> Editing an [LDAP-authenticated account](/manual/implementation/platform-usage/configuration/ldap.md) no longer clears its “LDAP” flag; the user now retains that status and remains visible in the [Users](/manual/implementation/platform-usage/configuration/users-and-roles.md) dashboard after an update.
> {% endupdate %}

{% update date="2025-06-09" tags="improvement,fix,changes,fixes" %}

## V2025.06

### API

> **New columns have been added to the response of the** [**Instance Information API**](/manual/implementation/platform-usage/api-reference/workload.md#informations)
>
> * "**type**": The instance type — either `"primary"` or `"replica"`.
> * "**port**": The listening port of the instance ([**requires Agent version 3.7+**](/manual/implementation/agent-usage/release-notes.md) 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](/manual/implementation/agent-usage/release-notes.md)

### :wrench: 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](/manual/implementation/platform-usage/log-files.md) section.
> * Resolved an issue with dynamic filters on the dashboard that affected the display of [registered users](/manual/implementation/platform-usage/configuration/users-and-roles.md).
>   {% endupdate %}

{% update date="2025-02-21" tags="feature,improvement,changes" %}

## 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](https://www.postgresql.fastware.com/blog/secure-ai-powered-by-fujitsu-enterprise-postgres-17sp1).\
> This ensures seamless compatibility and monitoring support for users running Fujitsu’s enterprise-grade PostgreSQL solution.
> {% endupdate %}
> {% endupdates %}


---

# 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/changelog/2025.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.