Observability

Observability shows what a deployed runtime is doing: health signals, workflow events, logs, model usage, and operational warnings.

Open a customer installation

For a CTO Team installation:

1. Open your LeenOps workspace.
2. Go to Workspace → People & teams.
3. Open CTO Team.
4. Select Installations.
5. Open the installation you want to inspect.
6. Select Observability in the installation navigation.

The direct route follows this pattern:

/teams/cto/installations/{deploymentId}/observability

What you can inspect

• Latest runtime health and connection state.
• Model usage captured for the installation.
• Recent workflow events.
• Runtime logs sent to the control plane.
• Warnings created by missing or unhealthy signals.
• Installation resources relevant to CTO observability.

Access requirements

• You must belong to the workspace that owns the installation.
• The CTO Team and installation must be available to that workspace.
• Your workspace role must allow you to view the team installation.
• The runtime must have completed installation and sent telemetry before panels contain data.

If the screen is empty

1. Confirm you opened the correct workspace and installation.
2. Check that the installation status is online.
3. Verify the Hermes or CTO runtime is running on the client machine.
4. Wait for the first telemetry interval after a new install.
5. Review Hermes troubleshooting.
6. If health remains empty, open a support request with the deployment ID and approximate time of the last successful connection.

Voice and SEO observability

Some products expose their own operational views. Voice conversation detail can show tool calls and integration results, while SEO continuous optimization has runtime health and workflow events. Start from the relevant product rather than the CTO installation screen.