-
Notifications
You must be signed in to change notification settings - Fork 16
spanName showing up as 'unknown' in New Relic when property exists #15
Comments
You bring up an interesting point. In the rule you mentioned:
This definition of
If you have time to test, I would love to know if this helps. I'm thinking that might need to become the default (or, something similar). |
@MrAlias Ok so I did some testing, none of which fixed the 'unknown' name issue:
Furthermore, I tried enabling debug logging on mixer to see if it would show me what it was sending to the NR handler. It does not, but it does show the template that it builds for the tracespans it sends:
This appears to be correct. I suspect that Mixer is not sending the correct SpanName, for some reason. However, with no way to see the traces going out of mixer/coming into the NR adapter, I can't verify this. If we had debug/trace logs that output the reports from Mixer, we could probably verify that. *Edit: Output from adapter showing what it is posting to NR:
Given (https://github.com/newrelic/newrelic-istio-adapter/blob/master/trace/handler.go#L86) - it seems almost certain that mixer is not sending the spanName, which is puzzling given that it sends |
Opened issue in Istio to see if they can give any insight: istio/istio#21411 |
Describe the bug
If I understand the tracespan template correctly, the following property should determine the 'name' of the trace span that shows up in New Relic:
This appears to be the case for most of my spans. I am running a multicluster setup, and I have spans that cross cluster boundaries. So, the 'destination' for the initial request in these spans is actually a ServiceEntry.
If I search for spans by the desired destination name (
productpage.bookinfo.mvp.global
in this case, I can see all of the unique spans, and they appear to be correct. However, the 'name' that they are assigned is 'unknown'. This is a bit puzzling, because according to the tags that are populated, I would think that thespanName
would have defaulted todestination.service.name
, asdestination.workload.name
is unknown:It may be the case that I just don't understand how exactly New Relic determines what the name of a span should be.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Span names are correctly set to the
destination.service.name
property.Version information (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: