Skip to main content

​
How Harmonia uses it

OpenTelemetry-compatible identifiers correlate web and worker operations. Structured JSON logs support diagnosis, Cloud Trace is the managed trace target, metrics summarize health and throughput, and durable usage records enforce model-budget policy.

OpenTelemetry

Propagation and correlation.

Structured logging

Machine-readable operational events.

Monitoring metrics

Health and workflow measures.

Usage and budgets

Pricing, reservation, and reconciliation.

​
Evidence status

Local tests prove identifier and record shape. Managed trace ingestion, alerting, and dashboards need authenticated cloud evidence; logs are diagnostic records, not workflow authority.

OpenTelemetry

How Harmonia propagates and records privacy-bounded execution traces.

Google Cloud Trace

How Cloud Trace is used as the target backend for correlated Harmonia execution traces.

Structured logging

How Harmonia logs operational outcomes without leaking prompts, content, or credentials.

Monitoring and metrics

How Harmonia exposes job health, agent activity, failures, receipts, and model usage to operators.

Usage and budget accounting

How Harmonia reserves model cost, records normalized usage, and fails closed on unknown pricing.
Last modified on August 26, 2026