The Orchestrators page lists all orchestrators associated with your account and listed by environment. Additionally, basic telemetry data is available on this page.
A green status ('Available') indicates the Orchestrator is up and running and successfully pulling its configuration from shared storage
A red status ('Unreachable') indicates the Orchestrator is offline and/or not pulling its configuration from shared storage
To view the telemetry data for a specific orchestrator, click the orchestrator ID.
Each orchestrator telemetry page displays graphs for the following:
Orchestrator metrics
Request Count: total number of all requests hitting the Orchestrator
Sessions: number of known sessions of downstream applications being proxied by the Orchestrator
Latency: duration of HTTP requests displayed as latency percentiles in milliseconds
Host system metrics
For evaluation, host system metrics are only available on Linux and Windows operating systems. They are not available on Mac OS X.
Memory utilization: amount of system memory being consumed by the Orchestrator.
CPU utilization: amount of host system compute being used by the Orchestrator.
Orchestrator charts are read only. Hover your mouse cursor over the charts for more details.
To adjust the polling time for Maverics to check for metrics from Orchestrator, change the polling parameter to the desired time (by default, 30 seconds) in your maverics.env file, (for example, export MAVERICS_POLLING_INTERVAL_SECONDS=5).
Observability settings
Log Level: Select the verbosity of the Orchestrator logs. For example, selecting "Error" will only show error logs (when debug mode is off).
Log Time Format: Select your preferred formatting of log timestamps.
Log Session Tracker: Enable or disable a session identifier in log messages. This setting is useful when filtering logs to isolate a problem with a particular session. (Note: The identifier printed in the logs corresponds to a particular session, but it is not the actual session ID itself and cannot be used to impersonate a user's session.)
Telemetry: When enabled, orchestrators send telemetry data to Maverics. You can view this on the Orchestrator Telemetry page. After you have started your Orchestrator, click Redeploy on a user flow to refresh. This option is turned on by default.
Orchestrator URL: (Required) This field is required when configuring the orchestrator as an OIDC or SAML provider. The orchestrator URL is used to define additional OIDC endpoints and SAML endpoints.
Logout Endpoint: This optional field is the endpoint clients may call to trigger logout from all applications and IDPs. Maverics can automatically populate this based on the Orchestrator URL. Enter the value after the orchestrator URL only (for example, slo or logout).
Post-Logout Redirect URL: This field is optional and represents the URL to redirect the client to after the single logout process is complete.Maverics can automatically populate this based on the Orchestrator URL.
Health check endpoint: Specify the endpoint that external services can poll to determine the health of the orchestrator. When a GET request is made to this endpoint, a live orchestrator should return an HTTP 200 response. If this field is not set, the default endpoint of /status is used. (Note: The orchestrator must be manually restarted in order for this change to take effect.)