Enabling Logging

Logging is enabled by default in all installations. To check that logging is enabled: Locate Thinfinity® Workspace Configuration Manager, select the Services tab and check that the Enterprise Logging option is selected.

Trace Files for the Gateway

When request or WebSocket tracing is on, the Gateway writes two trace files: Requests-YYYY-MM-DD.log and Websockets-YYYY-MM-DD.log, one of each per day. Earlier builds wrote one WebSocket trace file per process (Websockets-<pid>-YYYY-MM-DD.log); support bundles that span an upgrade day may contain both styles.

When the Gateway cannot append to an existing day’s file — for example, after an upgrade — the day’s rows go to numbered variants (Requests-YYYY-MM-DD.2.log, .3.log, up to .100.log); the newest by modification time is the one currently being written.

Tuning What the Gateway Traces

Three settings control the trace content.

Key	Default	Effect
`[Gateway]Metrics.Traces.Requests.StaticPages`	`false`	When off, requests the gateway’s web file server answers (static pages) are not written to the request trace. Turn on to include them.
`[Gateway]Metrics.Traces.Websockets.ToELog`	`false`	When on, every WebSocket connect, link, unlink and disconnect is also recorded as an Enterprise Logger event, independently of the trace file. These events use the Trace channel, which the default mask leaves off: to record them, also enable `0x02` in the Enterprise Logger channel mask (next row) — for example `0x57`. The actor these records name is the session’s unvalidated `rdpb_userid` cookie value — see the `rdpb_userid` note in Centralized Log Aggregation and Retention.
`[ELogs] EnabledMask` (Windows, `settings.ini`) / `elogs.enabled_mask` (Linux, `/etc/thinfinity/conf.d/settings.yaml`) / `global.elogs.enabledMask` (Helm)	`0x55`	Bitmap of which Enterprise Logger channels record events: `0x01` Audit, `0x02` Trace, `0x04` Analytics, `0x08` AppEvents, `0x10` VDI, `0x20` Booking. The default `0x55` leaves Trace off.