# 2023 {% updates format="full" %} {% update date="2023-09-01" tags="feature,improvement,fix,changes,fixes" %} ## V2023.07 #### Agentless Configuration > Enhanced provider selection functionality: added the ability to choose a provider from a predefined list of values.Added [Fujitsu Enterprise Postgres](https://www.postgresql.fastware.com/) as a new provider option when configuring a new instance. > > When selecting this provider, the port is automatically set to their default port. > > Improved visual representation by displaying the [Fujitsu Enterprise Postgres](https://www.postgresql.fastware.com/) icon alongside each relevant PG instance in Datasentinel’s navigation. {% @arcade/embed url="" flowId="wJnbgRP5pzrCUopsi4Wh" %} #### System Metrics > Introduced direct access to system metric dashboards via the [**pg\_instance**](/manual/features/tips-and-hints/tags.md) name, eliminating the requirement for the server name and resolving filter-related issues.\ > \ > [Real-time illustration ▶️](https://demo.datasentinel.io/d/0TincnYmz/server-ios?orgId=2\&from=now-1h\&to=now\&var-Filter=pg_instance%7C%3D%7Cpg-sales-3928@:9342) #### :wrench: Fixes * Improved scrolling functionality in the dashboard for file-systems with a large number of entries. Added the ability to sort file-systems by any property.\ [Real-time illustration ▶️](https://demo.datasentinel.io/d/WmQ4zUzMk/file-systems?orgId=2\&from=now-1h\&to=now\&var-Filter=pg_instance%7C%3D%7Cpg-sales-3928@:9342) * Inaccurate outcomes appear on the [Top Queries](/manual/features/key-features/top-queries.md) dashboard when multiple query IDs are associated with a single statement in pg\_stat\_statements. {% endupdate %} {% update date="2023-05-10" tags="feature,improvement,fix,changes,fixes" %} ## V2023.05 #### Tooling > Tooling is now available as scripts that can be run in a terminal window on one or multiple platforms, enabling you to collect information about Datasentinel’s configuration. {% content-ref url="/spaces/lcWi6G1jtNuyGT9C0pkc/pages/BkZpXiZyJgmgaAbAbaho" %} [Tooling](/manual/implementation/platform-usage/tooling.md) {% endcontent-ref %} #### Linux Compatibility > Datasentinel is now available on Red Hat Linux 9-compatible distributions such as **Rocky Linux 9** or **AlmaLinux 9** #### Python Version > The version of Python used for the backend and the agent has been upgraded to a more recent version, as well as the dependencies used. #### :wrench: Fixes * After updating the token for [Agentless](/manual/features/other-features/agentless-monitoring.md) connections, the [Live360](/manual/features/key-features/live360.md) module is no longer functioning. {% endupdate %} {% update date="2023-03-13" tags="feature,fix,changes,fixes" %} ## V2023.03 #### LDAP Authentication > Datasentinel seamlessly integrates with LDAP for user authentication. {% content-ref url="/spaces/lcWi6G1jtNuyGT9C0pkc/pages/eQk7zH7x5KBxZGHl1dnS" %} [LDAP](/manual/implementation/platform-usage/configuration/ldap.md) {% endcontent-ref %} #### :wrench: Fixes * [Live360](/manual/features/key-features/live360.md) does not work since upgraded to the version 2023.02 * When multiple parameter changes are detected, only the last one is displayed (needs agent v3.3) * Error when retrieving query texts of specific queries (python drivers) {% endupdate %} {% update date="2023-02-15" tags="feature,improvement,fix,changes,fixes" %} ## V2023.02 #### Lock Explorer > **Lock explorer** makes it easy to identify blocking sessions during blocked session issues, along with the associated queries and locks. > > By continuously monitoring lock activity, Datasentinel offers insights into your database’s state and assists you in addressing issues by generating blocking scenarios that give comprehensive information about lock activity during blocked session incidents. > > Learn about how this feature works by referring to the [Lock explorer](/manual/features/key-features/lock-explorer.md) documentation. > > [Real-time illustration ▶️](https://demo.datasentinel.io/d/fxjIaMt4z/blocking-scenarios?orgId=2\&from=now-1h\&to=now\&var-Filter=pg_instance%7C%3D%7Cpg-sales-3928@:9342) {% content-ref url="/spaces/lcWi6G1jtNuyGT9C0pkc/pages/mhBOCbdjDCCAyd5YvFOd" %} [Lock Explorer](/manual/features/key-features/lock-explorer.md) {% endcontent-ref %} {% hint style="info" %} To take advantage of lock explorer capabilities, ensure your agents are updated to at least version 3.0 or higher {% endhint %} {% @arcade/embed url="" flowId="1TJNUGSvNRHMRo6D3m3H" %} #### Session History > The dashboard displaying activity by **process id** has been replaced by a more accurate version, now showing activity by **user name** and **client host name**.\ > \ > [Real-time illustration ▶️](https://demo.datasentinel.io/d/f_vKcZLik/db-workload?orgId=2\&from=now-1h\&to=now\&var-Filter=pg_instance%7C%3D%7Cpg-sales-3928@:9342) #### Changed Parameters > Improved detection of changed parameters. A graphical annotation is now included in the main dashboard graphs to clearly indicate when a parameter change has been detected.
> > [Real-time illustration ▶️](https://demo.datasentinel.io/d/R1i7cnLmz/pg-instance-parameters?orgId=2\&from=now-1h\&to=now\&var-Filter=pg_instance%7C%3D%7Cpg-sales-3928@:9342) #### Collection Level > The Agent version 3.2, introduces the Collection Level feature allowing you to choose the metrics to monitor. {% content-ref url="/spaces/lcWi6G1jtNuyGT9C0pkc/pages/PU7809BSrcyBDPOEXxXT" %} [Collection Level](/manual/implementation/agent-usage/collection-level.md) {% endcontent-ref %} #### PostgreSQL > The embedded PostgreSQL database is now in version 14 during a full installation #### Fixes * Query and Session history reports do not complete if query texts cannot be integrated in the PDF. * Execution plans are not displayed when using pg\_store\_plans >=1.6 on a PostgreSQL cluster < 14. * Values of type **Decimal** returned from Postgresql cannot be serialized to JSON format when using the alerting module. {% 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/2023.md?ask= ``` 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.