The Diagnostics 2.4 release introduces popular exciting new features and capabilities. Please read on for more details and consult the release notes for a complete list.
Achieving good performance is easy on a system when there are only few users. But how is the scalability of your Smallworld system? Can it accommodate the growth of the user base? We have added a visualization that shows quantity (number of users) and quality (startup time) in one picture. The right bottom quadrant represents good scalability, because the application is started many times and still the startup is very fast. Diagnostics provides the insights to increase the scalability of your Smallworld system and this picture is where you can see the results.
A Disk Full error can occur even if there is plenty of disk space available on the database server. Proper superfile configuration is needed to facilitate datastore growth. When a Disk Full error occurs all users and connected systems will be impacted and lose productivity until the situation is resolved. Diagnostics now allows you to prevent Disk Full errors by monitoring the datastore growth and predicting when the limits are reached, helping you choose between 3 possible options to avert the downtime completely: tuning superfile configuration, cleaning old data references, performing ds transfer.
The operational and performance metrics gathered by Diagnostics on Smallworld may be stored together with metrics obtained from sensors in other applications. If Splunk is already used within your organization then you can onboard Diagnostics onto your existing Splunk cluster. If your organization already has another log management system in place, it is now possible to duplicate Diagnostics events as JSON objects in real-time so you can onboard them onto any other centralized logging database as well.
Please consult the release notes for more exciting new features.
Diagnostics. In control.