System Parameters
System Parameters are the global settings that tune how Nodinite behaves: how long data is kept, how new Log Databases are created, how messages are processed, what users see in Log Views, and which Web Client features are switched on. Each parameter is a key with a value, stored once per environment in the Configuration Database, and read by the Logging Service, the Monitoring Service, the Web Client, or the Web API.
Administrators change them in the Web Client under Administration › Settings › System Parameters — see Manage System Parameters.
The System Parameters list in the Web Client Administration area; select a key to view its description and edit its value.
How System Parameters Work
Configuration Database)] Table -->|cached ~15 s| LS(fa:fa-hard-drive Logging Service) Table -->|cached ~15 s| MS(fa:fa-watch-fitness Monitoring Service) Table -->|cached ~15 s| WC(fa:fa-globe Web Client) style Table fill:#e8f1fb
An administrator saves a value through the Web API; every service picks it up from the Configuration Database on its next read.
- No restart needed. Every process caches each value for about 15 seconds; a few parameters take effect on the next cleanup or processing run, or after a longer cache. Each parameter page states when its change takes effect.
- Administrators only. You must be a member of the built-in Administrator Role to change a value.
- Defaults are recommended. Change a value only when you know why; a wrong value can stop logging or monitoring.
Status markers in the lists below: 🔒 Read-only (set by the installer or another page), ⚠️ No effect (kept for compatibility), ❌ Obsolete (nothing reads it). Unmarked parameters are active.
Retention and Cleanup
How long logged data, audits, and monitoring history are kept. The Logging Service and the Monitoring Service delete expired data automatically.
- CleanUpTimerInterval – how often the Logging Service cleanup runs
- DaysToKeepMessageEventsDefault – event retention given to new Message Types
- DaysToKeepMessageDataDefault – message body retention given to new Message Types
- DaysToKeepMessageContextDefault – context retention given to new Message Types
- DaysToKeepErrorEventsWithoutData – retention for error events without data
- DaysToKeepLogAudits – retention for Log Audits
- MissingEventsDays – removes unprocessed events and orphaned BizTalk data
- DaysToKeepMonitorEvents – history of Resource state changes
- DaysToKeepMonitorAgentBackups – Monitoring Agent configuration backups
Log Databases
When a new Log Database is created, what it is called, where its files go, and who can access it.
- DaysToSplitDatabaseOn – create a new Log Database after N days
- SizeToSplitDatabaseOn – create a new Log Database above N GB
- LogDatabaseName – naming pattern for new Log Databases
- LogLocations – data and log file placement across disks
- LogDatabaseRecovery – SQL Server recovery model (SIMPLE or FULL)
- LogServiceUsers – accounts granted access to new Log Databases
- LogAccessRoles – database roles granted to those accounts
- AvailabilityGroupBackupPath – backup share for Always On Availability Groups
- DatabaseMaintenance – nightly index maintenance and archive shrink
- SqlPackageExecutable – path to SqlPackage.exe used for Log Database deployments
- SqlPackageParams – encryption and trust settings for those deployments
Message Processing
How the Logging Service processes logged events and their context.
- MessageProcessingBatchSize – events per processing batch
- MessageProcessingMaxBodySize – largest message body the Logging Service processes
- MessageProcessingTimerInterval – ⚠️ No effect
- ContextPropertiesFilters – drop unwanted context properties
- EDIMessageTypeParseString – Message Type names for EDIFACT messages
- LogStatusCodeAutoSyncPolicy – create or update Log Status Codes from incoming events
- AllowRepositoryAutomapping – build the Repository Model from Repository Binding
Log View Data Protection
What users see when they open logged events in a Log View.
- HideSearchFieldValuesInLogViews – hide Search Field values not configured in the Log View
- HideAdditionalFieldValuesInLogViews – show, hide, or mask built-in event fields
- ProtectedContextValues – mask selected context values
Repair and Resend
Whether users with the right Log View permissions can resend or repair messages.
- AllowResubmit – master switch for resend
- AllowRepair – allow repair before resend
- ResendWebhookSettings – resend to HTTP endpoints
- ResubmitContextValuesForActiveMQ – resend to ActiveMQ
Alarms
- AlarmQueueSettings – retries and timeout for the Alarm Queue
Web Client and Appearance
- EnvironmentName – environment name in the header and in database names
- EnvironmentColor – header colour per environment
- StylesheetScriptsEnabled – allow scripts in Stylesheets
- DashboardPluginSettings – sandbox for Custom Dashboard plugins
- AI – switch the AI features on or off
Repository and Content
- UseContracts – enable Contracts in the Repository Model
- DisableCustomFields – hide the legacy Custom Fields menus
- SharedFilePolicy – allowed file types and link behaviour in the File Library
- ReservedArticleTagNames – tags never copied onto new Snippets
Security and Access
- UseActiveDirectoryGroups – use Windows AD groups in Roles
- DefaultRolesInViews – Roles pre-selected on new Log Views, Monitor Views, and Diagram Sets
Licence, Installation, and Operations
Set by the installer, changed on another page, or changed only when Support asks.
- ProductKey – 🔒 Read-only; change it in Manage License
- CustomerName – 🔒 Read-only; change it in Manage License
- Version – 🔒 Read-only; the installed version
- SqlServer – SQL Server and Linked Server settings used to reach the Log Databases
- ProductArtifactsPath – where the Web API finds the Logging and Monitoring Services
- MaintenanceMode – Web API maintenance flag
Obsolete
Upgraded installations still show these keys; changing them has no effect.
- AllowExport – ❌ Obsolete
Note
Keys removed by the 7.x upgrade (for example
AdminRoleName,IMLoggingServicePath, orMaxNumberOfRowsReturnedInClientQuery) no longer exist and are not documented. Nodinite v6 is no longer supported.