> ## Documentation Index
> Fetch the complete documentation index at: https://docs.strata.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Telemetry

The Orchestrator produces three categories of observability data: **structured logs**, **OpenTelemetry metrics**, and **OpenTelemetry traces**. This section covers what the Orchestrator emits, how to configure each category, and where to send the data.

<Note>
  **Console terminology:** In the Maverics Console, Orchestrator instances and
  configuration delivery are managed through **Deployments**. When working directly
  with YAML, configuration is managed as files delivered via the `-config` flag or
  `MAVERICS_CONFIG` environment variable.
</Note>

## Observability Categories

### Structured Logging

The Orchestrator uses a single structured logger for all runtime output -- startup, configuration loading, authentication decisions, authorization decisions, session operations, health checks, errors, and more. Logs can be output in JSON format for machine parsing and forwarded to any log aggregation or SIEM system. Session ID correlation and field ordering provide consistent, searchable log entries.

### OpenTelemetry Metrics

The Orchestrator exports request, authentication, and runtime metrics via the OTLP protocol. Periodic readers push metrics to your OTLP endpoint at a configurable interval, giving you visibility into request volumes, error rates, latencies, and resource utilization.

### OpenTelemetry Traces

The Orchestrator supports distributed tracing via the OTLP protocol, providing end-to-end visibility into request processing through authentication and authorization flows. Trace data is exported to any OTLP-compatible backend.

## Telemetry Pages

<CardGroup cols={3}>
  <Card title="Logging" icon="file-lines" href="/reference/orchestrator/telemetry/logging">
    Structured operational and auth event logging with JSON output, filtering, and session correlation
  </Card>

  <Card title="Metrics" icon="chart-line" href="/reference/orchestrator/telemetry/metrics">
    OpenTelemetry metrics via OTLP for request, authentication, and runtime data
  </Card>

  <Card title="Traces" icon="diagram-project" href="/reference/orchestrator/telemetry/traces">
    OpenTelemetry distributed tracing via OTLP for end-to-end request visibility
  </Card>
</CardGroup>

## Health Check Configuration

The `health` key configures the health check endpoint and periodic heartbeat logging. The health endpoint is used by load balancers and orchestration platforms to verify the Orchestrator is running.

| Key                         | Type    | Default     | Required | Description                                                 |
| --------------------------- | ------- | ----------- | -------- | ----------------------------------------------------------- |
| `health.location`           | string  | `"/status"` | No       | HTTP path for the health check endpoint                     |
| `health.heartbeat.disabled` | boolean | `false`     | No       | Disable periodic heartbeat logging                          |
| `health.heartbeat.logLevel` | string  | `"info"`    | No       | Heartbeat log level -- `"info"` or `"debug"`                |
| `health.heartbeat.interval` | string  | `"60s"`     | No       | Heartbeat interval (duration string, e.g., `"60s"`, `"5m"`) |

The health endpoint responds with:

```json theme={null}
{"status": "up"}
```

The periodic heartbeat log entry includes the following fields: `orchestrator_version`, `config_version`, `cpu_count`, `cpu_usage`, `total_memory`, `memory_usage`, and `active_goroutines`.

<Note>
  Every log entry includes a [`soid`](/introduction/glossary#soid-secure-orchestrator-id) field for identifying and correlating logs by Orchestrator instance. See [Logging — Deployment Correlation](/reference/orchestrator/telemetry/logging#deployment-correlation) for details.
</Note>

## Cross-Reference

Configuration details for each telemetry category are on their respective sub-pages. For a step-by-step setup guide, see [Monitor and Observe](/guides/operations/monitor).

## Related Pages

<CardGroup cols={2}>
  <Card title="Monitor and Observe" icon="eye" href="/guides/operations/monitor">
    Step-by-step guide for setting up observability in production
  </Card>

  <Card title="Orchestrator Configuration" icon="sliders" href="/reference/orchestrator/configuration">
    Config file structure, environment variables, and runtime settings
  </Card>
</CardGroup>