Released: Jun 24, 2026

Aggiornamenti in 26.2.064

Funzionalità

• PostgreSQL Security & Compliance checks for logging and auditing configuration. Created a set of Security & Compliance (S&C) checks for PostgreSQL related to logging, security, and auditing configuration. The purpose is to validate whether PostgreSQL instances are configured according to recommended security and audit logging practices.
• PostgreSQL job for validating log_destination configuration. Introduced a new job for the PostgreSQL platform within the Security and Compliance area to validate logging configuration. The job checks whether the log_destination parameter is properly configured to ensure that server messages are captured. PostgreSQL supports multiple logging destinations such as stderr, csvlog, syslog, and jsonlog (and eventlog on Windows).
• PostgreSQL Security & Compliance checks for Access Control. Implemented new PostgreSQL Security & Compliance checks focused on Access Control. The checks should verify relevant PostgreSQL user, role, privilege, and authentication settings to help identify insecure access configurations and support compliance reporting.
• PostgresSQL Security & Compliance report. Implemented a PostgreSQL Security & Compliance Report that aggregates and presents the results from PostgreSQL Security & Compliance jobs.
• PostgreSQL Security and Compliance job templates. Created two new job templates for the PostgreSQL platform, equivalent to the existing Security and Compliance (MS SQL Server) – weekly and Security and Compliance (MS SQL Server) – weekly NO alerts templates.
• PostgreSQL job for validating log_filename configuration. Implemented a new PostgreSQL Security & Compliance job for validating the `log_filename` configuration parameter against CIS PostgreSQL Benchmark recommendations. The job verifies that the configured log file naming pattern complies with organizational logging policies and supports proper log rotation and audit log management. The implementation includes configuration validation, historical tracking, reporting, and graphical presentation of collected parameter values over time.
• PostgreSQL job for validating log_directory configuration. Implemented a new PostgreSQL Security & Compliance job for validating the `log_directory` configuration parameter against CIS PostgreSQL Benchmark recommendations. The job verifies that the configured log destination directory complies with organizational logging policies and ensures that PostgreSQL server logs are written to an appropriate and accessible location. The implementation includes configuration validation, historical tracking, reporting, and graphical presentation of collected parameter values over time.
• Added PostgreSQL Support for Security and Compliance Farm Views. Extend the existing Security and Compliance Farm Views framework to support PostgreSQL environments.
• Support for full CRON schedule in monitoring pause/ alerting pause.
• Added a configurable “deep” network logging. When a server has a heavy load of incoming messages we have no way of knowing what the messages are and what the source is. This provides a toggleable way of increasing logging.
• Added 'replacenone' function to replace NoValue with something in FDL. It will sometimes be useful to have the possibility to replace NoValue with something.
• Introduced new FDL properties for AG performance monitoring. Implemented a series of new FDL properties related to AG (Availability Group) performance monitoring. The update includes additional metrics and properties intended to improve visibility into AG performance behavior and provide extended monitoring capabilities for SQL Server Availability Groups within dbWatch Monitor.
• Differential Backup Monitoring Job for Microsoft SQL Server. Introduced a new monitoring job in dbWatch for Microsoft SQL Server that verifies the existence and freshness of differential backups (backup type I).
• Restrict access to autodiscovery. A user that is not allows to add instances, should not have access to the autodiscovery features.
• Improved graph documentation for MS SQL Server Performance Module. Updated and improved the documentation text (titles and descriptions) for graphs in the MS SQL Server Performance Module to ensure clearer explanations of what each graph shows and how to interpret the metrics.
• Saving instance config checks file write access. Saving an instance configuration with missing file write privileges will fail silently. This provides user feedback informing that the write failed.
• Async loading of job compatibilities.
• Oracle job “Table statistics check”: exclude temporary tables. Enhancements have been made to the Oracle job “Table statistics check”. The job has been updated to exclude temporary tables from the statistics evaluation, as these should not be part of regular statistics checks. In addition, the code has been improved to handle NULL values more robustly, ensuring that NULL values are no longer displayed in the details column.
• Defined is_multitenant property for Oracle 11 and earlier. In the Management > Storage section, the `is_multitenant` property is required to correctly display information about tablespaces and datafiles. For Oracle 11 and earlier versions, multitenant architecture is not supported. Therefore, this property should be explicitly defined with a static value of `0`. Currently, this property is not set for these versions, which results in missing or incomplete information in the Storage view (tablespaces and datafiles not being displayed).
• Metadata transferred correctly. In a Data Guard scenario, when a switchover occurs and job specification)is moved from the original primary to the new primary instance, engine jobs that rely on property-code (Java code executed before the procedure) no longer execute this code. The metadata related to property-code is not properly registered on the new primary instance. As a result, the job does not function as expected unless it is reinstalled. When switching back to the original primary instance, the job works as expected again. This affects jobs such as “PDB state monitor”, which rely on this functionality.
• Feedback on license overuse. It is possible to overuse a license when adding instances through ccc.
• Improved and standardized graph/table descriptions and layout (Oracle Performance). Enhanced and standardized descriptions and layout for graphs and tables in the Performance section of dbWatch Monitor for Oracle. The update includes improved descriptions, better consistency in terminology, and minor UI/layout adjustments to improve readability and usability. New graphs for SGA memory statistics, UGA / PGA (User memory statistics) and CPU load.
• Improved license summary in domain config.
• Enhanced PostgreSQL engine script to support procedure-based job execution. Improved the engine script for the PostgreSQL platform by introducing support for executing jobs implemented as stored procedures. A new execution procedure has been added to handle jobs written as PL/pgSQL procedures. At the same time, backward compatibility is maintained by continuing to support jobs implemented as functions. This ensures a more flexible and future-proof execution model while preserving compatibility with existing implementations.
• Corrected PostgreSQL job metadata for functions registered as procedures. Updated PostgreSQL platform job definitions where functions were incorrectly registered as procedures in job metadata.
• Increased authentication tag length from 96 to 128 in GCM setup.
• Improved CertID computation to reduce likelihood of collision.
• Improved Audit Configuration. Map audit policies to security groups for better usability. Currently audit policies are applied to specific servers/instances. This means new instances are not audited until it is explicitly added to the policy. By using security groups, there is less chance of “forgetting” to add auditing to an instance.
• Visual marking of content already added in AddContent dialogs. When configuring Service Group, Security Groups, Audit Policies it is difficult to tell what content is already added because it is still available in the add dialog.
• Improved exception handling in Blocking Statistics. If an error occurs in the final cleanup block, the same CATCH block may attempt to close/deallocate a cursor that does not exist or is already closed, potentially generating additional exceptions and masking the original error. Updated the procedure to verify that the cursor exists before attempting to CLOSE/DEALLOCATE it.
• New file size FDL Properties for MS SQL Server. Introduced new properties in FDL for Microsoft SQL Server that expose the size of database data files and transaction log files. These properties make it possible to visualize size of databases within dbWatch Web Server.
• Job Template view added mark when parameter override is in use.
• Refactored SQL Server Database Backup Check to Monitor Full Backups Only. Reviewed and simplified the existing SQL Server “Database backup” monitoring job so that it only validates Full Database Backups (backup type D).
• Changed default dbWatch database name from dbwatch to dbwatch_cc in remaining jobs. Updated remaining dbWatch jobs and related definitions that still use dbwatch as the default dbWatch database name, and change them to dbwatch_cc. This is a cleanup and consistency fix to align older job definitions with the current default database naming standard.
• Updated Wait Statistics job to remove history records with period value 0. Created a new version of the Wait Statistics job to clean up old history records where the period value is 0, as these can cause report generation errors such as division by zero. The procedure is also updated to prevent new records with period value 0 from being created.
• Improved Blocking Statistics job for MS SQL Server to avoid timeout. Updated the Blocking Statistics job for MS SQL Server to prevent timeout when there are several hundred blocked sessions. Instead of continuing to analyze all sessions, the job should stop after analyzing 50 sessions or after 20 seconds, whichever comes first.
• Flush instances with missing version or platform_info. Sometimes an instance is missing some fdl properties, typically platform_info and version. Detect if this happens, and flush the instance.
• Enhanced Database Disk Capacity job with default threshold percentages and automatic configuration of new disks. Update the SQL Server Database Disk Capacity job to add two new parameters: default warning percentage and default alarm percentage. These parameters should be used to automatically configure the existing threshold parameters warning threshold (percent), warning threshold (MB), alarm threshold (percent), and alarm threshold (MB). The job should also be improved to detect disks that are added after the job has been installed and automatically configure threshold values for those disks based on the new default percentage parameters, removing the need for manual updates to the existing per-disk threshold parameters.
• Reduced the number of in-memory events. The number of in-memory events can grow rather large, cap them at f.ex 1000 pr instance.
• Improved debug info in Connectivity dialog.
• Added a new internal graph for dbWatch Server memory usage. Create a new internal graph that shows memory usage for dbWatch Servers, making it easier to monitor server resource consumption over time.
• Added highlighting in charts when selecting a category. If a line chart has a lot of categories, they are almost impossible to tell apart. Added highlighting of the selected category.
• Job template editor should not allow editing of bundled templates. Today the editor allows you to change a bundled template, and then fails when trying to save (with a general save failed message).
• The reported memory usage gives a jigsaw pattern of memory increases and then down again after garbage collection.
• Configurable idle thread timeout. Currently there is a hardcoded 60 second threshold for when idle threads are killed. This is now configurable.
• Monitoring Gap detection properties. Introduced new properties that identify and expose monitoring gaps in historical data collection. The purpose is to detect periods where no monitoring data has been collected for an extended period of time, indicating potential issues with job execution.
• Update commons-lang3. Detected vulnerabilities CVE-2025-48924 in org.apache.commons:commons-lang3:3.17.0.
• Updated log4j to 2.25.3 or later.
• Upgraded jgit to version newer than 7.2.0×.

Correzioni

• Fixed SQL Server default database check job logic. Corrected “Logins default database check” job so the installed procedure now matches the documented behavior. The job now performs two separate checks: it verifies that only sysadmin logins are required to use master as default database, and it validates that login default databases both exist and are ONLINE. The fix also activates the return status for default db parameter and keeps the upgrade procedure in sync with the create procedure.
• Fixed missing Tablespaces and Datafiles in Management. In dbWatch Monitor, in the Management section, Oracle instances version 11 and earlier (including 10 and 9) did not display information under “Storage” for Tablespaces and Datafiles.
• SQL Performance (Oracle): Scroll bar overlap. In the SQL Performance package (Oracle), when opening “Show statistics”, the SQL statement statistics information is partially obscured by a scroll bar. This affects visibility of the content for all SQL statements and reduces usability of the view.
• Connecting to mongodb with forced tls. Mongodb connections with forced tls does not work.
• PostgreSQL instance setup: Login name resets when changing group selection. When adding a new PostgreSQL instance in dbWatch, after a successful connection, the user is prompted to select a database and create a new login. The GUI suggests a login name in the format `dbwatch_cc`, or `dbwatch_ccX` if the default already exists. However, if the user changes the group selection (top-level dropdown in the GUI), the suggested login name is reset to `dbwatch_cc`, regardless of the previously suggested or entered value. If the user does not notice this change and proceeds, and a `dbwatch_cc` login already exists, the installation will fail. Change to Test group … Database and Login values change.
• Report Editor: Custom logo/icons not shown in preview. In dbWatch Report Editor, logos/icons used in the report are no longer displayed in the preview window. The selected logo/image is still included in the generated report, but only when using PDF format. When HTML format is selected, the default dbWatch logo is used instead, even if a different logo has been configured. This behavior has never worked correctly in Control Center as far as we can recall, but it did work in dbWatch 12.
• NamedValues.remove( does not always work, causing a recursive loop when doing a reanchor when the reanchor types all ready exist in the NamedValues.
• Fixed bug in OrderedResult.compare method.
• h0 appears as a category in live multiserver fdl graphs.
• Missing audit trail for set worksheet/management authentication. There is no audit entry if a user changes his/her authentication in management or worksheet.
• Opening a Chat with no entries is stuck at “Loading”. When clicking on a chat with no entries the dialog view is stuck at “Loading”.
• Missing domain info in Monitor title. Sometimes the domain information is missing from the Monitor title.
• Uploading a new license gives incorrect warning. When uploading a new license, we sometimes see a incorrect warning claiming that the new license is not compatible with the current license usage.
• Server host resolves to 127.0.0.1. The fdl server/host (sometimes) resolves to 127.0.0.1.
• Adding a user with backslash breaks the users.json file. Adding usernames with json special characters (and perhaps xml) breaks the config files.
• Corrupted domain/<domain>/nodes.json after setting Server Display name using json escape characters.
• Getting task metadata through fdl never ends. Task metadata resolving never sends a ChannelEnd.
• Resetting password by editing config files does not rehash password. When changing the password by editing the authentication.xml file the password is not rehashed.
• Find default JDBC driver does not work. The “Find default” button under JDBC driver in instance configuration does not work.
• Using nested properties from an sql query is not robust.
• Bug in resolving of task maxversion. Maxversion of tasks always uses the task in local (if any).
• Resolved issues with metadata / metadata dictionary. Creating new entries in the metadata dictionary and then applying that metadata to instances is buggy. Values are not always applied.
• Audit Analyzer view has problems with multiserver mixed old/new audit. Audit Search never completes when mixed old and new audit.
• Missing refresh when changing template selection in Manage Jobs.