See everything. Miss nothing.

End-to-end OpenTelemetry with PDP/PEP decisions embedded in spans. Use Jaeger to slice by exact obligations (apigql.pdp.*), DSAR actions (apigql.dsar.action), and error signals. The screenshots below show real traces and how simple tag queries surface what matters.

Tip: In Jaeger Search, add Tags like apigql.pdp.allow=true or apigql.dsar.action=create. Think of it as “file-name-style” use-tagging: clear, consistent keys you can grep for later.

Telemetry slices & examples

Admin flow — full access

Jaeger trace showing admin PDP allow true with resource orders

Admin decision stamped into the span: apigql.pdp.allow=true, reason=admin full access, resource=orders.

PDP decision tags

Per-resolve decisions: apigql.pdp.action=read, apigql.pdp.resource.type=GraphQuery, plus tenant/workspace stamps for audit.

DSAR workflow traces

DSAR create/search traces filtered in Jaeger

Filter by apigql.dsar.action=create to list export/delete requests, then pivot into deep dependency graphs if needed.

Errors at a glance

Jaeger search results showing traces with error badges

Jaeger marks failed spans. Combine with http.status_code or error=true to triage quickly.

Use-tagging: find exactly what you want

Jaeger search using a custom tag filter to find DSAR create events

Search using tags like apigql.dsar.action=create or apigql.feature=ai. Consistent, “use-tagging” keys make reframing and recall trivial.

If any image doesn’t load, place the PNG next to this file or update the src path.