2025-05-01
New features
Orchestrator heartbeat
The Orchestrator now includes a heartbeat. This lightweight service logs runtime details at a configurable time interval. Enabled by default, the heartbeat service prints a log message containing the orchestrator ID, orchestrator version, orchestrator config version, as well as CPU count, usage, and total memory. By default, the heartbeat service logs at the info level.
The heartbeat service is part of the Health configuration block. It will be configurable from via user interface in an upcoming release of the Maverics Console. For more information, see Heartbeat.
Access logs enabled by default
HTTP access logs are now enabled by default. This change is meant to provide customers with greater insight into how requests flow through the system and can be used to confirm that all requests result in a corresponding response.
By default, access logs are logged at the debug level. If desired, access logs can be disabled via the orchestrator config. Access logs will be configurable from via user interface in an upcoming release of the Maverics Console. For more information, see Access Logs.
LDAP custom login page and localization
Orchestrator v0.111.0 introduces support for an optional custom login page when using LDAP as an IDP. By defining customLogin in the orchestrator configuration, the orchestrator delivers a custom HTML page stored in the filesystem.
In addition, the custom login page now supports standards-based language localization (BCP 47). By default, the localization selection is driven from the Accept-Language header, but can be customized to meet deployment specific needs.
LDAP custom login and localization will be configurable from via user interface in an upcoming release of the Maverics Console. For more information, see Custom Login.