Prometheus Metrics with Ambient Mesh using Istio Ingressgateway missing? #49676
Replies: 2 comments
-
Are the metrics in prometheus? |
Beta Was this translation helpful? Give feedback.
-
Hey - Thanks for the reply! From what I can tell, they aren't - istio_requests_total queries show objects in istio-system, but nowhere else. Try to limit that the namespace where I have an app deployed for testing and it fails to find anything. As a sanity check, verified the service name using a troubleshooting pod with a curl, and I get the homepage source successfully. In the Prometheus status for service discovery, istio-system is all good, but my namespace where the application is deployed shows as Dropped - But it works, using the same deployment for a mesh that is not running Ambient. Im not a Prometheus SME - I know enough to be dangerous and to query metrics here and there.... Its on my list of to-do's - need to get more in-depth with it. Im using the standard example Prometheus deployment from the OSS - but I changed a few items for persistent data / etc... But the base is still 99% from the OSS example. |
Beta Was this translation helpful? Give feedback.
-
If I deploy Istio without Ambient, all of my add-ons work as expected - Kiali graphs populate as expected - however, using the same add-ons using Ambient mesh, I am not getting any graph or traffic metrics in Kiali. There are no errors in Kiali and it does detect the mesh is using Ambient in the UI - Log shown below:
2024-03-02T16:33:23Z INF Kiali: Version: v1.80.0, Commit: 3a1118fa7fd23a155d19a250c11a4574bf0c094e, Go: 1.20.10
2024-03-02T16:33:23Z INF Using authentication strategy [anonymous]
2024-03-02T16:33:23Z WRN Kiali auth strategy is configured for anonymous access - users will not be authenticated.
2024-03-02T16:33:23Z INF Some validation errors will be ignored [KIA1301]. If these errors do occur, they will still be logged. If you think the validation errors you see are incorrect, please report them to the Kiali team if you have not done so already and provide the details of your scenario. This will keep Kiali validations strong for the whole community.
2024-03-02T16:33:23Z INF Initializing Kiali Cache
2024-03-02T16:33:23Z INF [Kiali Cache] Waiting for cluster-scoped cache to sync
2024-03-02T16:33:23Z INF [Kiali Cache] Started
2024-03-02T16:33:23Z INF [Kiali Cache] Kube cache is active for cluster: [Kubernetes]
2024-03-02T16:33:24Z INF [Prom Cache] Enabled
2024-03-02T16:33:24Z INF Create Tracing HTTP client http://tracing:80/jaeger
2024-03-02T16:33:24Z INF Server endpoint will start at [:20001/kiali]
2024-03-02T16:33:24Z INF Server endpoint will serve static content from [/opt/kiali/console]
2024-03-02T16:33:24Z INF Starting Metrics Server on [:9090]
I didnt see anything about changing Prometheus depending on what deployment was used (Standard / Ambient or Gateway API) - Did I just miss something??
Beta Was this translation helpful? Give feedback.
All reactions