Just like other logging tools, SmartInspect allows you to configure logging options via configuration files. But just how useful are configuration files on a production system really, when changes are only picked up when the application is restarted?
To make configuration files more useful in production environments, we added a new feature to SmartInspect 3.0 that allows you to periodically reload changes in your configuration file. Here is how it works: you create an instance of a new SmartInspect monitoring class and use it to watch for changes in a configuration file in a given time interval. Once this class detects that the monitored configuration file has been changed, it will automatically reload the file and apply the new configuration to the SmartInspect logging classes.
This is really great for systems where you want to enable or disable logging on the fly without restarting them (think about web applications and similar server systems). With the new configuration file monitoring class, this has become a lot easier. You just need to change the configuration file and SmartInspect will automatically reconfigure itself.
Also, remember the session configuration support in yesterday’s posting? By combining this with the configuration file monitoring, SmartInspect 3.0 will also allow you to dynamically configure and update your sessions. One interesting use case of this feature is to temporarily enable logging for a specific application module or user session that you want to diagnose.
Next in our series on new SmartInspect 3.0 features is the new protocol support for asynchronously logging.
Customer Portal
SmartInspect 3.0 Configuration File Monitoring
Just like other logging tools, SmartInspect allows you to configure logging options via configuration files. But just how useful are configuration files on a production system really, when changes are only picked up when the application is restarted?
To make configuration files more useful in production environments, we added a new feature to SmartInspect 3.0 that allows you to periodically reload changes in your configuration file. Here is how it works: you create an instance of a new SmartInspect monitoring class and use it to watch for changes in a configuration file in a given time interval. Once this class detects that the monitored configuration file has been changed, it will automatically reload the file and apply the new configuration to the SmartInspect logging classes.
This is really great for systems where you want to enable or disable logging on the fly without restarting them (think about web applications and similar server systems). With the new configuration file monitoring class, this has become a lot easier. You just need to change the configuration file and SmartInspect will automatically reconfigure itself.
Also, remember the session configuration support in yesterday’s posting? By combining this with the configuration file monitoring, SmartInspect 3.0 will also allow you to dynamically configure and update your sessions. One interesting use case of this feature is to temporarily enable logging for a specific application module or user session that you want to diagnose.
Next in our series on new SmartInspect 3.0 features is the new protocol support for asynchronously logging.