Ben Leggett

> Ambient has a more distinct separation of L4 and L7. It seems the push is that there should be complete L4 reporting such that telem consumers could get a...

> * This should be sufficient if the different components report to distinct metrics. For example, ztunnel writes just to TCP metrics and waypoints write only to request metrics. Otherwise...

> Adding a new label "reporter_component" to OSS ambient adds to its complexity and is not consistent with OSS Istio, which does not have this new label. That's not necessarily...

> From a cursory glance (caveat that I haven't fully read all the comments) I'd expect that reporter="source" and reporter="destination" should generally retain similar usage and not be overloaded with...

Related: https://github.com/istio/istio/issues/49841

As far as tracking features like this (or anything else with a proposed stabilization path), at the very least for every feature proposal I'd like to see: - We have...

> 2024-02-07T03:38:59.937210Z WARN inbound{^[[3mid^[[0m^[[2m=^[[0mda468de6f15cfd1539e6af8a9f7c707a ^[[3mpeer_ip^[[0m^[[2m=^[[0m10.244.138.36 ^[[3mpeer_id^[[0m^[[2m=^[[0mspiffe://cluster.local/ns/bookinfo-1-39307/sa/bookinfo-productpage}: ztunnel::proxy::inbound: connection to 10.244.138.16:9080 failed: Connection refused (os error 111) dur=112.7µs 2024-02-07T03:38:59.937356Z WARN proxy{^[[3muid^[[0m^[[2m=^[[0m0cbc3388-4ec7-4c35-b963-67e83bb82e12}:outbound{^[[3mid^[[0m^[[2m=^[[0mda468de6f15cfd1539e6af8a9f7c707a}: ztunnel::proxy::outbound: failed dur=2.932183ms err=http status: 503 Service Unavailable > >...

I have not had a chance to look at the failure on my end, but it might be worth comparing the test setup here to what @ilrudie is doing in...

Also @saiskee just reminded me that @howardjohn had already opened https://github.com/istio/istio/issues/46682 to actually remove the use of bookinfo tests from the ambient suites in favor of directly using `echo` instances,...

What provider? Is it related to this? https://github.com/istio/istio/issues/47575