Skip to main content

v5.3.0

Release date

9th April 2025

Improvements​

  • New Recommendations screen. This new screen provides users with personalized suggestions about DBmarlin itself and the instances which are being monitor. Recommendations can be resolved or hidden, with the option to unhide or mark them as unresolved at any time.
  • New “Explain Limit” field under Database instance settings. Can be set to 0 to disable plan capture for specific instances if required. Default value: 20, Valid range: 0 to infinity.
  • Smarter Defaults for Data Sources and Hosts
  • When defining a new datasource or host, default values for the selected instance type will now be auto-filled for improved efficiency.

Fixes​

  • Fixed instance sorting in Reports.
  • Adjusted chart dependencies to better align Activity data with Executions.
  • Resolved multiple issues with exported tables in both Reports and Hosts.
  • Fixed the Statement Table in Activity Comparison Reports that wasn’t updating correctly and had a sorting issue.
  • UI fix for SQL Statistics.
  • Addressed known timezone issues on the Events and SQL Explorer pages.
  • Resolved bugs related to the Send to Co-pilot button.
  • Fixed a bug in Login Settings where the same tag value couldn’t be used under different tag names.
  • Several minor fixes in Reports, including:
  • Instance dropdown not sorting correctly
  • Snapshot dropdown appearing too wide

Known Issues​

  • Some ongoing issues with UTC timezone handling are still present and will be addressed in version 5.4.
  • If you are monitoring a server which requires TLS v1.0 or v1.1 which are now obsolete you will need to edit ./lib/security/java.security to change disabledAlgorithms and restart the DBmarlin Tomcat. See this FAQ for more details.
  • Instance sorting in reports is incorrect and will be addressed in an upcoming update.
  • The statement table does not update correctly on Activity comparison reports; a fix is planned for version 5.3.
  • For CockroachDB Transaction Contention monitoring, it is possible that you could see a duplicate key warning the log file. This warning is related to aggregation of this data failing. The impact of this is that in the UI, you will only be able to see Transaction Contention data if the interval size is 1 hour or less (E.g. 5 mins, 15 mins). This would be the default when looking at a period of 1 day. For longer time ranges you will not be able to see data. This will be fixed in v5.4 of DBmarlin.