LogServiceUsers - System Parameter
LogServiceUsers lists the service accounts that the Logging Service gives access to on each new Log Database. Each account gets the database roles in LogAccessRoles. It is one of the System Parameters applied in How a new Log Database is created.
At a Glance
| Property | Value |
|---|---|
| Key | LogServiceUsers |
| Data type | string (accounts, separated by semicolons) |
| Default | Empty |
| Read by | Logging Service |
| Takes effect | Within about 15 seconds; no restart needed. Applies to the next Log Database the Logging Service creates. |
| Status | ✅ Active |
| Since | Nodinite 3; renamed from ImLogServiceUsers in Nodinite 7 |
How It Works
When the Logging Service creates a new Log Database, it gives every account in this list access with the roles in LogAccessRoles. The two parameters work as a pair: LogServiceUsers says who, LogAccessRoles says what. Existing Log Databases are not changed.
Assigning access needs the securityadmin server role (or sysadmin) for the Logging Service account. Without it, a DBA must grant access by hand after each new Log Database; see SQL Server Sysadmin Requirements.
Important
List every distinct service account that the Nodinite Core Services run as. Accounts that are missing can't read or write the new Log Database.
Value Format
A semicolon-separated list of Windows accounts in DOMAIN\Account form, without spaces:
DOMAIN\ServiceUser1;DOMAIN\ServiceUser2
Choosing a Value
- Include the accounts of the Logging Service, the Monitoring Service, and the application pools of the Web API and Log API; list each account only once. Following least privilege, list no other accounts.
- Each account needs a login on the SQL Server instance that hosts the Log Databases.
- Update the list whenever you change a service account, before the next Log Database is created.
Frequently Asked Questions
Can I assign access rights manually?
Yes, and you must when you create Log Databases manually or the Logging Service lacks securityadmin. Grant the LogAccessRoles roles to these accounts; the SQL rights for the Log Database and the Prerequisites & Permissions checklist on the Core Services page list what each service needs.