RA-7777: Implement logging of timing events in the trillian ctfe #1
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.
Changes made:
This PR implements comprehensive request tracing infrastructure for the Certificate Transparency Frontend (CTFE), enabling end-to-end tracking of HTTP requests through to backend Trillian gRPC calls with structured logging and correlation IDs. It is supported by the changes made in this PR digicert/trillian#1
Testing:
Prerequisite: I was testing in the local k8s cluster so need to port forward to the pods.
1. Basic Service Health Check
Expectation: We should get results. This is a sanity check to make sure nothing has broken.
Request
Logs
2. Request with Custom Transaction ID
Expectation:
Request
Logs
Test 3: Multiple Requests for Timing Analysis
Expectation:
Requests
Logs