-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Rename operation name for activator's proxy span and queue-proxy's span #7934
Conversation
Currently both activator's proxy span and queue-proxy's proxy span have same name `proxy`. It is alright to see one trace data. But it is difficult to find/filter it by operation name. Hence, for example, if we want to find the trace which _activator is in the path_, we cannot filter it.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nak3 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The following jobs failed:
Automatically retrying due to test flakiness... |
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.
/lgtm
@@ -266,7 +266,7 @@ func TestActivationHandlerTraceSpans(t *testing.T) { | |||
t.Errorf("Got %d spans, expected %d", len(gotSpans), tc.wantSpans) | |||
} | |||
|
|||
spanNames := []string{"throttler_try", "/", "proxy"} | |||
spanNames := []string{"throttler_try", "/", "activator_proxy"} |
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.
Should we rename "throttler_try"
to "activator_wait"
while we're at it?
Proposed Changes
This patch renames operation name for activator's proxy span and
queue-proxy's span.
Currently both activator's proxy span and queue-proxy's proxy span
have same name
proxy
for operatioin. It is alright to see the trace data.(We can distinguish the
proxy
, but...)But it is difficult to find/filter it by the operation name.
(We cannot filter it as both are same name)
Hence, if we want to find the trace data which activator is/isn't in the path,
we cannot filter it.
Release Note