Guides
Send conduction as OpenTelemetry logs
Turn on private telemetry, point it at a Collector and read the SDLC Analytics indicators per maestro and per team.
Turn it on and check it
Telemetry sends the events Orkastery already writes to the ledger as OpenTelemetry logs, over OTLP/HTTP JSON. Opt-in is private to the person or the machine, is off by default and does not change orkastery.yaml.
ork telemetria ligar creates the private ork.telemetria-config/v1 file, outside the repository, with 0600 permissions. It only stores the choice and a stable random pseudonym; endpoint and headers stay in the process environment.
OTEL variables alone do not turn the feature on. When it is off, ork telemetria status and ork telemetria enviar return before enumerating threads, opening ledgers or reading endpoints and headers.
ork telemetria ligar
ork telemetria status
ork telemetria desligarPoint it at a Collector
Set OTEL_EXPORTER_OTLP_ENDPOINT, to which Orkastery appends v1/logs, or OTEL_EXPORTER_OTLP_LOGS_ENDPOINT, used exactly as given; the logs one wins. The same precedence applies to headers, as key=value pairs. An invalid value is refused without being echoed.
Sending is manual, through ork telemetria enviar. The cursor is incremental per ledger and only advances after remote confirmation: delivery is at least once, and the consumer deduplicates by log.record.uid.
The reference models live in templates/telemetria: collector-otlp.yaml for a generic OTLP/HTTP destination, collector-loki.yaml for Loki’s OTLP base and the Grafana dashboards for conduction, prompts and Collector health. The dashboards do not pin a URL or a datasource.
The public receiver ships without TLS or authentication. Use a trusted network and apply a private overlay with TLS and authentication before exposing it.
export OTEL_EXPORTER_OTLP_ENDPOINT=http://collector.example:4318
ork telemetria enviar --dry-run
ork telemetria enviarCheck before sending
ork telemetria status --json shows where the activation comes from, the destination without credentials, the pending bytes per thread, the last confirmed UID and any terminal rejection.
ork telemetria enviar --dry-run ignores the stored cursor and shows the already redacted request, from the start or from the --offset byte. It does not resolve headers, use the network or write the cursor.
ork telemetria status --json
ork telemetria enviar --dry-run --json
ork telemetria enviar --dry-run --offset <byte> --jsonAttributes and correlation with the runtimes
Each LogRecord uses attributes from a closed list: service, vcs, cicd and gen_ai from the OpenTelemetry conventions, user.hash with the pseudonym and the orkastery.* attributes for thread, phase, dispatch, mode, decision, claim, receipt and runtime. Heartbeats and fields outside the list do not become attributes.
Each successful dispatch produces orkastery.ledger.phase_dispatch, with session.id in Claude Code or conversation.id in Codex. Orkastery does not re-emit native events or bodies.
The dispatched session gets an ephemeral configuration that turns off prompts, responses and tool details in the runtime’s native logs. Endpoint and headers never go into argv or the ledger.
Prompt content
With opt-in on, the text only comes from the file stamped by phase_prompt_recorded, checked against the recorded SHA-256. Before the LogRecord, the core removes secrets (literal, separated, in Base64 and in nested JSON), applies dado_privado and checks again.
The remaining text goes out in gen_ai.input.messages, under the ork.telemetria-redacao/v1 policy. A missing file, an unsafe path, a size above the limit or a hash mismatch becomes a typed gap, with no prompt, path or hash; a transient error or a removal failure stops before the event, and the cursor does not advance.
The GenAI 1.37.0 conventions used are in Development status. The content can be sensitive, and the company that receives the logs sees the text left after removal; that is why opt-in is explicit and private.
Indicators per maestro and per team
ork telemetria maturidade computes six agentic indicators over the machine’s ledgers, in the window between --desde and --ate, with no network or opt-in: receipt coverage on merges, sustained first truth, CHECK rework, decisions, questions and reversals, policy exceptions and mode usage.
Only the first two are rates; the others are counts or distributions, each with its own coverage and gaps. No indicator becomes a composite score, a weight, a ranking or a target, and an incomplete historical event does not become a negative.
The projection emits the ratified orkastery.sdlc.analytics.result.v1 event, with numerator, denominator, coverage and gaps. The dashboard sums those fields by user.hash and by service.namespace, the team assigned by the policy, without recomputing the formulas; without a team, the policy marks team_source_missing.
The DORA measures stay separate, with their own pipeline and closed schema, and come out as not confirmed without an external deployment and incident linked to the proven merge. Equivalence of the Loki queries remains not confirmed.
ork telemetria maturidade --desde <ISO> --ate <ISO> --json