Version 1.9.12.62 Changes

Log Changes

This version adds a number of new log writer option checkboxes which may be enabled.

These new items allow generic emulator messages to be separately logged from Probel messages which tend to generate much more content.

Note that the auditing log entries will also include the source IP of the request as well as the name of the authenticated user. Also, AuditGet will generate much more data than AuditSet. If you are primarily concerned with tracking when users make changes AuditSet should be sufficient. For a comprehensive security audit logging configuration, some additional items should also be enabled including: AccessViolations, LoginFailures, and LoginSuccesses. Additionally, if Probel is used, enabling ProbelEmulatorsRouteChangeRequestReceived will track route change requests from Probel emulators.

Custom Log Messages

This version also adds the ability to generate your own log message subscriptions:

Clicking the new Add Custom button will open a dialog for generating your own log entry.

This dialog allows you to create a new log entry. The log entry is made up of a log entry name, and id which must be between 80001 and 99999, a severity, and a valid SapV2 subscription message. The subscription message allows you to define specific system changes that will generate this log message. This allows you to create a custom log entry to a specific device, panel, or specific properties which might not be exposed in the default options.

Once added it will be presented as a checked item under the new Custom group in the log items checkbox tree. Note that unchecking a custom item will delete it after selecting apply and so it will have to be recreated if you want to add it to the log writer again.