Ambient/Telemetry/Waypoint - 'unknown' destination labels in metrics #56526
Unanswered
jan-ludvik
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have Istio 1.26.1 in ambient mode. We enabled ztunnel and everything is fine on that layer.
Now we started with Waypoints and they seem to work for us but we get strange behavior in metrics.
We often get series looking like this. I redacted some names but basically source labels are fine but destination labels are missing. I even found a case where we had metrics from one waypoint and one series had all destinations tags fine and the other one had all of them
unknown.I can still figure out the destination namespace because I know where the waypoint is but I wonder what we have wrong.
This seems to happen a lot with headless service (although I don't have that 100% confirmed because I don't know the destination service name) but I found cases where it happened in namespaces where we don't have headless service.
In other words - what can make waypoint fail to add destination labels (from the namespace where it is located) to the metrics?
Beta Was this translation helpful? Give feedback.
All reactions