Pratik Mankawde 2644179a42 ci: Rule C — read Grafana tempo datasource, enforce span-scope filter tags ...

Rule C was reading docker/telemetry/tempo.yaml (the Tempo server config), which
has no filter tags, so it always SKIPped — L3 was silently unenforced. The
trace-search filter tags actually live in the Grafana datasource provisioning
file (docker/telemetry/grafana/provisioning/datasources/tempo.yaml) as
search.filters[].{tag,scope}. Point Rule C there (server file as fallback),
pair each tag with its scope, validate only span-scope tags against L1 (resource/
intrinsic tags like service.*/name/status/duration are exempt), and strip the
TraceQL span. prefix.

On phase-9 this turns "SKIP: C" into "OK: C: 24 tempo span-filter tags all in
L1" — L3 is now genuinely guarded. Adds a RuleCTempo test class (4 cases:
span-tag-not-in-L1 flagged, span-tags-pass, resource/intrinsic ignored, skip
when datasource absent). 83 tests total.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-11 19:28:24 +01:00

..

levelization

layering

2026-06-11 18:01:18 +01:00

otel-naming

ci: Rule C — read Grafana tempo datasource, enforce span-scope filter tags

2026-06-11 19:28:24 +01:00

rename

build: Create single test binary xrpl_tests (#7327)

2026-06-05 19:24:32 +00:00

strategy-matrix

ci: Make configurations launch on certain event types (#7447)

2026-06-10 18:08:34 +00:00

check-pr-description.py

ci: Add workflow to check PR description has been filled (#6965)

2026-04-20 12:12:58 +00:00

format-inline-bash.py

style: Run shfmt on workflows, actions and markdown bash code (#7333)

2026-05-27 19:24:18 +00:00