Version 1.9.12.62 Changes
Last updated
Last updated
Warning: This version represents a feature freeze of any new features in the 1.9.x beta branch in preparation for a new release. During the final beta period, only bug fixes will occur in the 1.9.x branch prior to a 1.10 release. Any new feature work will now move to a new 1.11.x beta version.
This version adds a number of new log writer option checkboxes which may be enabled.
| Device Emlator Log Items | Description |
|---|---|
GenericEmulatorsLastReceived | Last received message only from generic type emulators |
GenericEmulatorsLastSent | Last sent message only from generic type emulators |
ProbelEmulatorsLastReceived | Last received message only from Probel type emulators |
ProbelEmulatorsLastSent | Last sent message only from Probel type emulators |
ProbelEmulatorsRouteChangeRequestReceived | Log requests for route changes coming from Probel emulators. Message will display change as <source>x<destination>. |
These new items allow generic emulator messages to be separately logged from Probel messages which tend to generate much more content.
| Message Logging Items | Description |
|---|---|
AuditSet | Log incoming SAPv2 messages that are requesting changes for security audit purposes |
AuditGet | Log incoming SAPv2 messages that are requesting information for security audit purposes |
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.
Warning: This dialog is designed to be used in consultation with support staff. It must use a valid SAPv2 subscription message. Also using aggressive messages can affect performance as the system tries to log excessive information. Please consult with support when using this feature.
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.
