In Norwegian we have one word: robustifisering. In English that word is a phrase, to make something more robust. With this most recent update, we’ve worked hard with ‘robustifisering,’ with improved reliability across a wider range of system configurations and operating environments.
Read the full release notes in the dbWatch Wiki.
Improved support across Windows configurations
First, there’s better support for different Windows configurations. We’ve implemented changes that improve monitoring reliability across a wider range of Windows configurations, including configurations involving accessibility features. Now only the winter weather may freeze you, but your windows configuration won’t freeze in your monitoring view.
Improved recovery in large virtual environments
dbWatch now handles temporary Virtual Machines (VM) freezes and connection interruptions more effectively, particularly in large environments where backup processes may affect many systems simultaneously.
Auditing the Management Layer Beta Version
There is an important distinction between database auditing and auditing the tool being used to manage the database. Database-native auditing can tell you what happened inside the database: access to objects, changes to data, permission activity and other events supported by the database platform.
dbWatch is a privileged operational tool. DBAs can use it to monitor systems, investigate problems, and perform management tasks. In larger environments, many people may have access to different parts of the same dbWatch installation.
That creates another useful audit question: What did the users of the database management system do?
The dbWatch audit functionality provides a higher-level record of activity. It shows administrators who has been using dbWatch and tracks actions performed through the product.
For a small DBA team, that may simply make troubleshooting easier. If something changed, you have another source of information for reconstructing what happened.
For a large enterprise or MSP, it becomes much more significant. You may have dozens of people working across hundreds or thousands of databases. Different users may have different permissions and responsibilities. In that environment, operational accountability becomes part of running the estate properly.
Extending Security & Compliance to PostgreSQL
PostgreSQL support in the Security & Compliance package continues to improve with around 20 checks implemented from an expected set of roughly 45 at the time of writing. The reporting framework and surrounding functionality are already in place, while additional checks still need to be completed.
That also means we would like more real-world testing.
If you are running PostgreSQL and already use dbWatch, particularly if security and compliance are important in your environment, this is a good opportunity to try the functionality and tell us what you find. Real database environments are considerably more interesting than test environments.
Seeing Better in Dark Mode
dbWatch Control Center now has a dark interface option, giving users another way to work with the client and making long sessions easier on the eyes.
A More Robust dbWatch
Taken together, these updates are about making dbWatch more reliable and easier to work with across different environments. Or, to borrow the Norwegian word once more: a little more robustifisering.
