Skip to main content
The Orchestrator exports metrics via OpenTelemetry using the OTLP protocol. Metrics are collected through periodic readers that push to your OTLP endpoint at a configured interval.

What Metrics Are Emitted

The Orchestrator exports metrics across two categories:
  • Request metrics — Total requests, response status codes, and request duration histograms. These give you visibility into traffic volume, error rates, and latency distribution.
  • Runtime metrics — Process-level metrics such as memory usage and concurrency data. These help you right-size Orchestrator instances and detect resource constraints.
Additional orchestration metrics — including authentication events, connector health, and policy evaluation data — are planned for future Orchestrator releases. The metrics available today focus on request-level and process-level observability.
The specific metrics available depend on your Orchestrator version. Consult your Orchestrator’s actual OTLP output to confirm which metrics are exported in your deployment.

Configuration

If you manage Orchestrator configuration through the Maverics Console, advanced telemetry settings require the config override feature. Config override requires enablement for your organization — contact your Strata account team or Strata support to enable it.
Configure periodic readers to export metrics to your OTLP endpoint:
maverics.yaml
telemetry:
  metrics:
    readers:
      - periodic:
          exporter:
            otlp:
              protocol: "http/protobuf"
              endpoint: "http://otelcol.example.com:4318/v1/metrics"
              insecure: true
              timeout: 5000
          interval: 5000
FieldDescription
protocolOTLP transport protocol — use "http/protobuf"
endpointYour OTLP collector’s metrics endpoint URL
insecureSkip TLS verification when connecting to the collector
timeoutExport timeout in milliseconds (default: 5000)
intervalCollection and push interval in milliseconds (default: 5000)

OTLP Export

All metrics are exported via OTLP (http/protobuf), the OpenTelemetry standard protocol. Any OTLP-compatible backend can receive these metrics, giving you full flexibility in your observability stack:
  • OpenTelemetry Collector — The reference collector that can fan out to multiple backends
  • Grafana Alloy — OpenTelemetry-compatible collector for the Grafana stack
  • Datadog Agent — Enable the OTLP receiver on the Datadog Agent to ingest metrics directly
  • New Relic — Send OTLP metrics to New Relic’s OTLP endpoint
  • Honeycomb — Native OTLP ingestion for metrics and traces
  • Dynatrace — OTLP ingestion via the Dynatrace API
If you use Prometheus, configure your OpenTelemetry Collector to receive OTLP and export to Prometheus using the prometheusremotewrite exporter.

Periodic Reader Settings

The periodic reader controls how frequently the Orchestrator collects and pushes metrics:
  • Interval — How often metrics are collected and exported (default: 5000ms). Lower intervals provide more granular data but increase network and collector load.
  • Timeout — Maximum time to wait for an export to complete (default: 5000ms). If the collector is slow or unreachable, the export is abandoned after this timeout.

Advanced Configuration

The periodic reader’s OTLP exporter supports additional options for production environments including TLS, compression, custom headers, and aggregation preferences.
maverics.yaml
telemetry:
  metrics:
    readers:
      - periodic:
          exporter:
            otlp:
              protocol: "http/protobuf"
              endpoint: "https://otelcol.example.com:4318/v1/metrics"
              timeout: 10000
              compression: "gzip"
              headers:
                - name: "x-api-key"
                  value: "your-api-key"
              certificate: "/etc/ssl/certs/otel-ca.pem"
              temporality_preference: "delta"
          interval: 10000
FieldDescription
compressionCompression type — "gzip" or "none"
headers[]Custom HTTP headers sent with each export request (array of name/value pairs)
certificatePath to CA certificate for TLS verification of the collector
client_certificatePath to client certificate for mTLS authentication
client_keyPath to client private key for mTLS authentication
temporality_preferenceAggregation temporality — "cumulative", "delta", or "lowmemory"
default_histogram_aggregationHistogram strategy — "explicit_bucket_histogram" or "base2_exponential_bucket_histogram"

Configuration Reference

Periodic Reader

KeyTypeDefaultRequiredDescription
telemetry.metrics.readers[].periodic.exporter.otlp.protocolstringYesOTLP protocol — "http/protobuf"
telemetry.metrics.readers[].periodic.exporter.otlp.endpointstringYesOTLP collector endpoint URL
telemetry.metrics.readers[].periodic.exporter.otlp.insecurebooleanfalseNoSkip TLS verification when connecting to the collector
telemetry.metrics.readers[].periodic.exporter.otlp.timeoutinteger5000NoExport timeout in milliseconds
telemetry.metrics.readers[].periodic.intervalinteger5000NoCollection interval in milliseconds
telemetry.metrics.readers[].periodic.exporter.otlp.compressionstringNoCompression type — "gzip" or "none"
telemetry.metrics.readers[].periodic.exporter.otlp.headers[]array[]NoCustom HTTP headers sent with each export request. Each entry has name and value fields.
telemetry.metrics.readers[].periodic.exporter.otlp.certificatestringNoPath to CA certificate for TLS verification of the collector
telemetry.metrics.readers[].periodic.exporter.otlp.client_certificatestringNoPath to client certificate for mTLS authentication
telemetry.metrics.readers[].periodic.exporter.otlp.client_keystringNoPath to client private key for mTLS authentication
telemetry.metrics.readers[].periodic.exporter.otlp.temporality_preferencestringNoAggregation temporality — "cumulative", "delta", or "lowmemory"
telemetry.metrics.readers[].periodic.exporter.otlp.default_histogram_aggregationstringNoHistogram aggregation strategy — "explicit_bucket_histogram" or "base2_exponential_bucket_histogram"
The SDK spec also supports pull readers, but they are not commonly used with OTLP push-based export. The periodic reader is the recommended approach for exporting metrics to an OTLP collector.

Example

Console UI documentation is coming soon. This section will walk you through configuring this component using the Maverics Console’s visual interface, including step-by-step screenshots and field descriptions.

Advanced Example

Console UI documentation is coming soon. This section will walk you through configuring this component using the Maverics Console’s visual interface, including step-by-step screenshots and field descriptions.