Create child spans for mixer check calls#1593
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
This seems odd. The labels say “report” while calling istio-policy, should say check? |
|
@mandarjog Yes, that is a separated problem. I am going to fix it as well, and I think the problem is in policy's sidecar config? |
|
@mandarjog Yes, that's a bug. Check/Report are swapped: https://github.com/istio/istio/blob/master/pilot/docker/envoy_telemetry.yaml.tmpl |
|
PR out istio/istio#5283 |
|
Why is there two Check calls on the first hop? |
|
@kyessenov One from Ingress and one from productpage sidecar. |
|
Reminder: These PRs should be against the 0.8 release branch, instead of master. Please re-open against the correct branch (as master is now locked). |
|
Should ingress itself also not have a span? |
|
Yes, ingress tracing has issues, too, I think. My expectation is that the
check should be on a span that reaches ingress service, not the outbound
call from ingress. That's not how it looks on the chart. Additionally, we
should probably try a gateway as well.
…On Sat, Apr 28, 2018, 2:12 PM Douglas Reid ***@***.***> wrote:
Should ingress itself also not have a span?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1593 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJGIxgTXsLitR1lWJD7nTCJjS_j3MLlbks5ttNs-gaJpZM4TrRs0>
.
|
|
Close this one with another one open in 0.8 branch: #1610 |

No description provided.