Skip to main content

v6.5.0

Release date

4th June 2026

Improvements​

  • Alerting multiple improvements:
    • Multiple severity levels each with their own threshold (info, warning, critical)
    • Change rule evaluation frequency
    • Change the alert rule evaluation window length
    • Scope rules matching multiple instances by multi-select or by tag
    • Scope rule matching multiple hosts
    • Metric preview chart to see how often the alert rule would have triggered
    • Alert rules can have different notifications set per rule.
  • Integration Settings multiple improvements to alert notifications:
    • Integration Settings screen is now organised by type (Alert notifications, APM integrations and AI integrations).
    • New 'Test Now' button for testing notification integrations like Email, WebHook, Slack, PagerDuty and ServiceNow.
    • For each of the Alert notifications you can now have 2 or more ‘Profiles’ defined (previously you could only have 1 of each type). For example you might have email profiles for different teams and in the Alert Rule choose the profile that you want the alert to go to.
  • Ask AI Co-pilot button on Activity screen to analyse all data on the screen for the selected time range including wait events, SQL, alerts, change events. Can summarise what happened in the period, trends and any issues seen and how to fix.
  • Blocking Sessions screen has a new chart - blocked time by session ID.
  • DBmarlin Infrastructure updates to latest versions of Tomcat, Nginx, PostgreSQL, TimeScaleDB and Java.
  • Script to pull down JDK to run tools like jmap, jstat, jcmd, jstack bundled under scripts/utilities. Useful for troubleshooting Tomcat issues.

Fixes​

  • Data Migrator could fail with a Deadlock.
  • Security improvements

Known Issues​

  • Object statistics for Oracle may contain only partial information, such as table names, but may be missing index and column names. This can be improved by increasing oracle.jdbc.ReadTimeout in Advanced Connection Settings for the sensor.
  • If you are monitoring a server that requires TLS v1.0 or v1.1 (now obsolete), you will need to edit ./lib/security/java.security to change disabledAlgorithms and restart DBmarlin Tomcat. See this FAQ for more details.