-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Implement monitoring for Istio #1931
Comments
After short research it looks that in order to send metrics from istio mesh to our external monitoring instances we need to:
|
We should first ensure Istio usage and future. |
12 tasks
5 tasks
Closing because of deprecation of Istio component. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We would like to monitor parameters of Istio (control plane and envoy proxy) on unmanaged clusters deployed with Epicli.
In compare to managed cluster (AKS/EKS) Istio pods are working in internal cluster network which is not accessible by external prometheus server win epiphany.
Describe the solution you'd like
We would like to scrape metrics from Istio Control Plane and Envoy Proxy in our external Prometheus service (monitoring machine). In order to make it, we should implement schema with Prometheus Federation.
I would like to have Prometheus locally in cluster which scrape metrics from Istio components and external Prometheus should be able to get metrics using Ingress Gateway as endpoint and the mentioned local Prometheus .
Describe alternatives you've considered
Deploy node port service without local prometheus and federations.
Additional context
How to monitor Istio using external Prometheus: link
The text was updated successfully, but these errors were encountered: