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
{{ message }}
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
The evaluation of the expression checking the B3 header interpreted the
integer string as a duration instead of a string. Instead evaluate
against an empty string as this will equivalently result in false if
the header is not present.
Resolvesnewrelic#14
Describe the bug
Using the default install of the istio adapter with Istio 1.4.3 produces the following error in Mixer:
Thus preventing the adapter from receiving trace spans from Mixer.
Changing the
"0"
in the 'newrelic-tracing' rule to""
in the following location resolves this issue:With this change to the rules I can see trace spans populating in New Relic One now.
This seems to be an issue with the second argument to the OR function -
"0"
- being interpreted as a 'Duration' rather than a 'String' (which is the type of the first argument in this case) in Mixer's rule parsing code: https://github.com/istio/istio/blob/master/mixer/pkg/lang/ast/expr.go#L232-L251To Reproduce
Steps to reproduce the behavior:
Expected behavior
Istio can send trace spans to the adapter with the default rules
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: