Overview

Monitoring gives platform administrators a live technical view of the Ender Turing system itself — how the underlying components are behaving, rather than what is happening in your conversations.

The page embeds a monitoring dashboard directly inside Ender Turing so you do not need to open a separate tool or remember a separate address. It is a viewing surface only: nothing on this page changes your Ender Turing settings, analytics configuration, or conversation data.

Monitoring is aimed at administrators of self-hosted installations. Everyday users — reviewers, team leaders, agents — never need it, and it does not appear in their navigation.

How It Works

Where to find Monitoring

Open Settings from the main navigation.
In the Settings menu, select Monitoring.

Monitoring sits near the bottom of the Settings menu, below System, separated from the entries above it by a divider, and is marked with a gauge icon.

When the Monitoring entry appears

The Monitoring entry is not always present. Three conditions must all be true before it shows up in the Settings menu:

Condition	What it means
System Configuration (Manage) permission	Your role must grant System Configuration with Manage access. Superusers always qualify.
Single-tenant installation	Monitoring covers system-level components, so the entry is hidden in multi-tenant deployments.
The `monitoring` service is running	The entry appears only while every container of the `monitoring` service is up.

If the entry is missing, work through those three conditions in order. The service condition is the one most likely to change day to day — see Services to check whether monitoring is running and to start it if it is stopped.

Two things can block that check:

Services sits under Settings → Apps, which needs Marketplace Configuration or Integrations Configuration access. System Configuration (Manage) on its own does not reveal Apps in the Settings menu, so ask an administrator who has one of those permissions to check the service for you.
Services lists only services that have been downloaded and activated. If monitoring has no row at all, it is not installed rather than merely stopped: download and activate a monitoring version on the System page first, then start it from Services.

Navigation is built once when Ender Turing loads in your browser, so starting or stopping the monitoring service does not add or remove the entry while you keep working. Refresh the page after the service change to see the updated navigation.

Who can use Monitoring

Actor	What they can do
Administrator with System Configuration (Manage)	Sees the Monitoring entry (when the other two conditions hold) and can open and read the dashboard.
Superuser	Same as above — superusers satisfy the permission check automatically.
Any user without System Configuration (Manage)	Does not see the entry. Opening the page by direct address is refused and lands on a "not authorised" page instead.

There is no partial or read-only variant of this page for other roles: either you have System Configuration access and see the full dashboard, or you cannot reach the page at all.

Reading the dashboard

The monitoring dashboard is embedded as a display-only view that fills the page, so you see the panels and charts themselves rather than a second product interface wrapped around them.

Everything you interact with belongs to that embedded view. Ender Turing does not add controls of its own to this page, and it does not carry over anything you have selected elsewhere in the product: filters, team selections, and date ranges from Conversations or Dashboard have no effect here. Which controls the dashboard itself offers depends on the monitoring version installed on your system.

The System tabs on this page

Monitoring is served from within the System area of the product, so the page header shows the System title and the System tab strip (System, Speech Recognition Quality, Anonymization, and ASR Instances where available).

Monitoring itself is not one of those tabs. Clicking any tab in the strip navigates away from the monitoring dashboard — open Settings and select Monitoring again to come back.

Related system views

A separate Logs entry sits directly below Monitoring in the Settings menu. It is gated the same way — System Configuration (Manage), a single-tenant installation, and the logging service running. Because the two entries depend on different services, one can be visible while the other is not.

Logs behaves differently from Monitoring once you open it: instead of embedding the viewer in the page, it opens the log viewer in a new browser tab, leaving Ender Turing on the page you were using.

Things to Keep in Mind

Monitoring reflects system health, not conversation analytics. For quality, volume, and agent metrics, use Dashboard, Charts, or C-Level Boards instead.
Stopping the monitoring service hides the page. If an administrator stops that service on the Services page, the Monitoring entry disappears from navigation once the page is refreshed, and comes back the same way after the service is fully running again.
The dashboard is unavailable while the service is down. The permission check that guards the page does not depend on the service, so an administrator who reaches the page while monitoring is stopped will not get a working dashboard.
Nothing here is destructive. Viewing the dashboard has no effect on transcription, analytics, or stored conversations.