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
I'm using nginx-ingress integration with opentracing and Datadog and it works fairly well.
One issue I have is that the span name seems to only be the path of the request.
As my nginx-ingress is configured with a lot of ingresses (with a lot of different hostnames ), it makes it difficult to know which host was called exactly without looking in the attributes.
What does the community think about having the span name formatted as HOST-PATH - METHOD ?
The text was updated successfully, but these errors were encountered:
I'm using nginx-ingress integration with opentracing and Datadog and it works fairly well.
One issue I have is that the span name seems to only be the
path
of the request.As my
nginx-ingress
is configured with a lot of ingresses (with a lot of differenthostnames
), it makes it difficult to know which host was called exactly without looking in the attributes.What does the community think about having the span name formatted as
HOST-PATH - METHOD
?The text was updated successfully, but these errors were encountered: