Repository navigation
Configure OpenTelemetry collection and export in the reference implementation #91
Description
Production-harden the reference implementation by wiring OpenTelemetry collection and export end to end.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
sabasiddique1 commentedon Sep 14, 2026
I would like to take this. Plan: an OTLP exporter behind the Guardian's envelope-log sink, span names from
specification/v0.1.0/trace/otel-mapping.json(which #63 completes), a collector config underreference-implementations/agt/, and a test that asserts every emitted span name is a key in the mapping. Will open the PR againstintegrationthis week.rocklambros commentedon Oct 5, 2026
@sabasiddique1, your plan from September 14 is the right shape and I'd like you to run with it. I'm assigning #91 to you.
Some context on why the clock just started. The Responsible AI Institute's TrustX team is evaluating ACS as a verification target for their lab, and they asked for OpenTelemetry output from the reference Guardian by about October 12, ahead of a demo on October 23. They want a file they can analyze offline, so a file exporter option (OTLP/JSON to disk) next to the collector config would cover them.
Scope for the 12th, as I see it: OTLP span export fed from the same point as the envelope log sink, with span names and attributes from otel-mapping.json. Add the acs.decision span event with its current attributes plus reason_codes, policy_references, and chain_hash as extras (I'm filing an issue for those today), and keep your test that every emitted span name is a key in the mapping. Emit for the hooks the reference handles today. OCSF can wait.
#63 was stuck behind triage. #57 is accepted now, so that gate should clear, and I'll get the Spec leads to pick the OCSF class so you can finish it.
Can you commit to the 12th? If the answer is no or only partly, say so here and we'll split it. Our weekly call is Thursday at 10am Mountain and you're welcome on it (the invite is pinned in the OWASP Slack channel). Thanks for sticking with this one!
sabasiddique1 commentedon Oct 8, 2026
@rocklambros yes, all of item 1, confirmed in the Slack thread. Working version Monday Oct 12, PR done Oct 16. I've added Bar's acceptance points from the thread to the plan.
One scoping note: span names and required attribute names come from otel-mapping.json at runtime, but the mapping doesn't say which envelope field feeds each attribute, so that part lives in a small table in code. A renamed span or attribute needs no code change; a new attribute source does.
Explain how the reference Guardian produces a trace, with diagrams (#280
Release 0.1.4 (#281)
Export Guardian traces as OTLP to a file and over HTTP (GenAI-Securit…