Skip to content

fix: improve testnet OTEL verification#55

Merged
AquiGorka merged 1 commit intomainfrom
fix/testnet-otel-verification
Apr 14, 2026
Merged

fix: improve testnet OTEL verification#55
AquiGorka merged 1 commit intomainfrom
fix/testnet-otel-verification

Conversation

@AquiGorka
Copy link
Copy Markdown
Contributor

Summary

Two fixes for testnet OTEL trace verification:

  1. verify-otel shared trace IDs: Changed from >= 5 to >= 1 shared trace IDs, and added a check for zero orphaned provider trace IDs. Testnet runs produce a single unified distributed trace (1 trace ID shared across SDK + provider), unlike Docker tests which create multiple traces per bundle.

  2. testnet-verify ingestion wait: Added 60s wait before OTEL verification in the lifecycle script. Without this, the final spans (e.g., withdraw) haven't been flushed to Grafana Cloud Tempo when verification starts.

What's NOT affected

  • Docker-based OTEL tests (e2e/verify-otel.ts) use Jaeger with a separate code path — unaffected by these changes.
  • Local Docker test suite (./test.sh otel) verified passing after change.

Test plan

  • Run testnet E2E + verify-otel (suites 1+2) — should pass with 17/17 checks
  • Run testnet lifecycle + OTEL (suite 4) — should pass with ingestion wait

- verify-otel shared trace IDs: assert >= 1 (not 5) and check for
  zero orphaned provider trace IDs. Testnet runs as a single unified
  trace, unlike Docker tests which create multiple traces per bundle.
- testnet-verify: add 60s ingestion wait before OTEL verification to
  allow Grafana Cloud Tempo to ingest the final spans.
@AquiGorka AquiGorka merged commit f56fa3f into main Apr 14, 2026
1 check passed
@AquiGorka AquiGorka deleted the fix/testnet-otel-verification branch April 14, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant