Could not fetch health #5295
Replies: 15 comments 37 replies
-
(converted to github discussion) If prometheus is in a different namespace, and you are getting that error message (which indicates Kiali is still trying to find prometheus in istio-system namespace) then your Kiali CR is still not configured correctly. Please see this and make sure the configuration is correct: https://kiali.io/docs/configuration/p8s-jaeger-grafana/#prometheus-configuration You did not post your Kiali CR yaml so we cannot confirm whether what you have is correct or not - but one thing is to always check the indentation. We often see Kiali CRs simply misconfigured due to poor/misaligned indentation. To confirm the validity of your Kiali CR, see: https://kiali.io/docs/configuration/kialis.kiali.io/#validating-your-kiali-cr |
Beta Was this translation helpful? Give feedback.
-
Hi @jmazzitelli |
Beta Was this translation helpful? Give feedback.
-
The A couple things to look at:
|
Beta Was this translation helpful? Give feedback.
-
Hi @jmazzitelli I am using version 1.49.0. In terms of modification I can confirm there has not been any manual modification. Also the installation is standalone kiali installation. |
Beta Was this translation helpful? Give feedback.
-
Error from pod 2022-07-08T09:08:55.992586006Z2022-07-08T09:08:55Z ERR Error fetching availability of the tracing service: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: lookup tracing.istio-system on 10.69.0.10:53: no such host" Received following output kubectl kiali kiali -n istio-system -o jsonpath='{.spec}' |
Beta Was this translation helpful? Give feedback.
-
@lucasponce that's correct. We have not installed Jaeger. |
Beta Was this translation helpful? Give feedback.
-
We would prefer not to install it. Are you referring to kiali cr file as Kiali configuration? If yes, we don't have any reference of jaeger in the cr file. I have shared the cr file already, You can have a look. |
Beta Was this translation helpful? Give feedback.
-
I made a mistake in my previous instructions - I forgot the command "get" and you should examine the "status" (not spec) field. So run this:
(this assumes the CR is in the namespace |
Beta Was this translation helpful? Give feedback.
-
I have made a few changes to the CR file. |
Beta Was this translation helpful? Give feedback.
-
Now when I run the following |
Beta Was this translation helpful? Give feedback.
-
Okay from the top, I am using the following commands to install standalone kiali I am installing the latest version. If for standalone installation there is not any CR file then how kiali will point to prom grafana on different namespace. |
Beta Was this translation helpful? Give feedback.
-
do you have any reference for value.yaml file? So that I can point kiali to different namespace for prom and grafna |
Beta Was this translation helpful? Give feedback.
-
I don't see how you are installing the latest version. The latest version of Kiali is 1.53.0 - see https://github.com/kiali/kiali/releases and the helm chart repo here https://kiali.org/helm-charts/index.yaml Yet, your screenshot shows v1.49.0: So I still think you are not installing what you think you are installing. (I hate to harp on the "read the docs" thing - but... did you update your local helm repo as per the Kiali installation docs here: https://kiali.io/docs/installation/installation-guide/install-with-helm/#adding-the-kiali-helm-charts-repository where it says, "If you already added the repository, you may want to update your local cache to fetch latest definitions by running: |
Beta Was this translation helpful? Give feedback.
-
Sorry trial and error. If either works!
…On Tue, 19 Jul 2022, 19:07 Nick Fox, ***@***.***> wrote:
Looks like both your grafana/prom urls are the same:
http://grafana-prometheus.monitoring:80. Is that correct?
—
Reply to this email directly, view it on GitHub
<#5295 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIWJIBS3T56S7O45JEG2URDVU3VHFANCNFSM526CGETQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
This issue can be closed. |
Beta Was this translation helpful? Give feedback.
-
Hi,
Promethus and Grafana dashboard configured in different namesapce is unable to communicate with kiali dashboard. Hence graph is not loading. Configured cr.yaml file but URL is still pointing to istio-system namespace.
Error: Could not fetch health: Error while fetching app health: Post "http://prometheus.istio-system:9090/api/v1/query": dial tcp: lookup prometheus.istio-system on 10.69.0.10:53: no such host
Any idea?
Beta Was this translation helpful? Give feedback.
All reactions