-
Notifications
You must be signed in to change notification settings - Fork 270
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to change OcCollector Service name via LINKERD2_PROXY_TRACING_S… #2856
Allow to change OcCollector Service name via LINKERD2_PROXY_TRACING_S… #2856
Conversation
bc8fe0c
to
952951a
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2856 +/- ##
==========================================
- Coverage 67.68% 67.63% -0.05%
==========================================
Files 332 333 +1
Lines 15158 15182 +24
==========================================
+ Hits 10259 10269 +10
- Misses 4899 4913 +14
... and 14 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
linkerd/app/src/env.rs
Outdated
@@ -249,6 +249,8 @@ const ENV_OUTBOUND_HTTP1_CONNECTION_POOL_IDLE_TIMEOUT: &str = | |||
|
|||
const ENV_SHUTDOWN_GRACE_PERIOD: &str = "LINKERD2_PROXY_SHUTDOWN_GRACE_PERIOD"; | |||
|
|||
const ENV_PROXY_TRACING_SERVICE_NAME: &str = "LINKERD2_PROXY_TRACING_SERVICE_NAME"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the sake of consistency, we already have:
pub const ENV_TRACE_ATTRIBUTES_PATH: &str = "LINKERD2_PROXY_TRACE_ATTRIBUTES_PATH";
can we call this LINKERD2_PROXY_TRACE_SERVICE_NAME
and group the definitions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
c934687
to
3fd2bf1
Compare
…ERVICE_NAME env variable Signed-off-by: GrigoriyMikhalkin <[email protected]>
…CE_NAME Signed-off-by: GrigoriyMikhalkin <[email protected]>
3fd2bf1
to
0ffe5c5
Compare
@alpeb Do i understand it correctly that it was already implemented(by a different approach) in linkerd/linkerd2#13130? So this PR can be closed, i assume? |
Correct, we should be able to close this PR now. |
Solves linkerd/linkerd2#11157