Skip to main content

v4.8.0

Release date

9th Sep 2024

Important

If you have authentication disabled you can ignore this.

This release introduces RBAC (Role-base Access Control) for DBmarlin users. By default any users you create will have no permissions granted to them unless they are an admin user in which case they can do everything.

If you already created any DBmarlin users, after upgrading to 4.8.0, your existing users will all be regular (non-admin) users and will therefore have access to nothing. You should create one or more admin users using the scripts provided (dbmarlin-add-user.sh and dbmarlin-add-user.bat).

Once logged in as an admin user, you can grant access to any other users through the UI under Settings -> Logins.

Improvements​

  • Alerts can now go to ServiceNow.
  • Role-base Access Control for DBmarlin users.
  • SQL Server Tempdb can now be enabled/disabled under Advanced Settings.
  • You can now choose a subset of databases for which to send data to New Relic. Not currently a UI setting so if you need this contact support.
  • Host metrics for SQL Server and SQL Azure via SQL query.
  • Cockroach transaction contention new chart and additional data.
  • Keep selected period when opening in a new tab.
  • Added Cockroach SQL statistic: retries.
  • Removed hard-coded PHYSICAL_READ_REQUESTS from Oracle SQL statistics query.

Fixes​

  • Clicking View button on Host Settings no longer goes to 'Page Not Found'.
  • Invalid column name MODIFIED_EXTENT_PAGE_COUNT reported to tomcat log.
  • Pasted URL not working correctly UTC vs local time.
  • Backend errors like HTTP 400 now correctly reported at frontend and don't redirect to /login.
  • Login button text no longer missing on Mobile devices.
  • SQL Server - additional overtime charts chart - all had incorrect units in tooltips.
  • SQL Explorer - changing date selector clears e.g. instance & metric fields.

Known Issues​

  • For earlier versions of SQL Server you may see Invalid column name 'MODIFIED_EXTENT_PAGE_COUNT' reported to DBmarlin tomcat log which can be ignored.
  • 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.