Repository navigation
feat(observability): Add OpenTelemetry tracing for traffic decisions and lease operations - #16
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
Closes #6
This PR introduces OpenTelemetry tracing for the distributed traffic-control workflow and Redis-backed lease operations. It also adds a local Jaeger setup for inspecting traces and documents the tracing configuration and verification steps.
Changes
ObservationRegistryinto the traffic decision engine and Redis lease coordinator.docs/open-telemetry.mdcovering instrumentation, configuration, local setup, testing, and troubleshooting.Validation
POST /api/v1/traffic/evaluateand received anALLOWEDresponse.distributed-traffic-controlservice and traces appeared in Jaeger.Further inspection of the custom span hierarchy and the Redis lease-acquisition path is needed to confirm that every intended operation is represented correctly.
Documentation
See
[docs/open-telemetry.md](https://chatgpt.com/g/g-p-6a79a4ad81088191b64779ba4aeebe75-open-source/c/docs/open-telemetry.md)for setup instructions, configuration details, and troubleshooting.