Cluster Manager Maintenance
The Cluster Manager Maintenance configuration category includes the following configurable options:
Audit Log Broker Channel Name
Audit Log Broker Enabled
Always Write to Cluster Manager Log
Audit Log Database Async Writes
Audit Log Database Enabled
Request headers to store
Reload Scripts on Module Config Save
Transaction Log Retention (Days)
Scheduler Thread Count
Heartbeat Persist Frequency MS
Stats Cleanup Frequency MS
Stats Persist Frequency MS
Support writes to LOB columns
|
|
Audit Log Broker Channel Name |
|
|
|
| STRING | |
| The audit logs will be sent to the specified topic/queue name. Must be non-empty. | |
|
|
smilecdr-audit
|
|
|
|
|
Audit Log Broker Enabled |
|
|
|
| BOOLEAN | |
| This setting may be used to submit all audit log events to a message queue. | |
|
|
false
|
|
|
|
|
Always Write to Cluster Manager Log |
|
|
|
| BOOLEAN | |
Forces Smile CDR to always send audit logs to the cluster manager audit database, even if another module of type audit is defined. Normally, creating such a module would disable the builtin audit log in the cluster manager. Setting this setting to true will cause all audit log events to be written to both databases.
|
|
|
|
true
|
|
|
|
|
Audit Log Database Async Writes |
|
|
|
| BOOLEAN | |
| If enabled, writing to the audit log will be performed asynchronously, resulting in potentially shorter transaction times and a more efficient use of the database. An in-memory asynchronous queue is used, meaning that there can be a small delay between an auditable action occurring and the audit log being written. | |
|
|
false
|
|
|
|
|
Audit Log Database Enabled |
|
|
|
| BOOLEAN | |
| This setting may be used to disable saving audit logs to all event writers if it is not needed in a given solution design. | |
|
|
true
|
|
|
|
|
Request headers to store |
|
|
|
| STRING | |
| This setting can be set to a comma-delimited list of header names that the audit service will extract from the request and store with any Audit Log. | |
|
|
| (no default) | |
|
|
|
Reload Scripts on Module Config Save |
|
|
|
| BOOLEAN | |
| If enabled, when module configuration is saved via the Web Admin Console or the Admin JSON endpoint, then all scripts in that configuration will be reloaded on the server where the save occurred. This allows javascript developers to quickly test changes to scripts on a standalone development server without having to restart the module. Note this will only reload the script on the process where the save occurred. If you need to reload scripts in a module running in a cluster, you should restart the module. | |
|
|
false
|
|
|
|
|
Transaction Log Retention (Days) |
|
|
|
| NON_NEGATIVE_INTEGER | |
| The number of days that entries in the transaction log should be retained before being deleted from the database. If blank, the transaction log will be retained indefinitely. | |
|
|
7
|
|
|
|
|
Scheduler Thread Count |
|
|
|
| POSITIVE_INTEGER | |
| The number of threads allocated to processing Scheduled Jobs (both local and clustered). See Scheduler Performance for more information. | |
|
|
4
|
|
|
|
|
Heartbeat Persist Frequency MS |
|
|
|
| POSITIVE_INTEGER | |
| How often module health status is persisted to the database | |
|
|
15000
|
|
|
|
|
Stats Cleanup Frequency MS |
|
|
|
| POSITIVE_INTEGER | |
| How often module performance statistics are deleted from the database and collapsed into time interval statistics. Should be greater than stats.stats_persist_frequency_ms | |
|
|
300000
|
|
|
|
|
Stats Persist Frequency MS |
|
|
|
| POSITIVE_INTEGER | |
| How often module performance statistics are persisted to the database. Should be greater than or equal to stats.heartbeat_persist_frequency_ms | |
|
|
60000
|
|
|
|
|
Support writes to LOB columns |
|
|
|
| BOOLEAN | |
| If enabled, will still write to pre-migration LOB columns when supported. | |
|
|
true
|
|
|