You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After discussion with @heaths , I am adding an item to enable distributed tracing in test-proxy. We should take the opportunity to utilize structured logging for these messages as well.
When flag --distributed-trace is passed, the proxy should generate trace messages in stdout that other applications can consume.
This will probably require a refactor of logging in general in the proxy to get all these outputs figured out
The text was updated successfully, but these errors were encountered:
scbedd
added
Test-Proxy
Anything relating to test-proxy requests or issues.
and removed
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
labels
Mar 5, 2025
This will probably require a refactor of logging in general in the proxy to get all these outputs figured out
Not necessarily. We could optionally trace from the existing ILogger messages and if you wanted to keep tracing compatible, perhaps those would log a specific trace field that could be used for identification e.g., log = "existing messages, new lines and all". I could start with that and it wouldn't prevent future growth possibilities.
After discussion with @heaths , I am adding an item to enable distributed tracing in test-proxy. We should take the opportunity to utilize structured logging for these messages as well.
When flag
--distributed-trace
is passed, the proxy should generate trace messages in stdout that other applications can consume.This will probably require a refactor of logging in general in the proxy to get all these outputs figured out
The text was updated successfully, but these errors were encountered: