-
Notifications
You must be signed in to change notification settings - Fork 775
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
Loki integration Issue #2916
Comments
hi @KaustubhKishore , can you share what error you are facing while adding the data source in grafana , you can see this at bottom |
hi @KaustubhKishore , please use this "http://loki.monitoring.svc.cluster.local:3100/" and let me know if it solves your issue. I have also raised a pull request to update the same. |
Hi @dk03051996 , The url you are suggesting has already been tried, we'll try it once more on a fresh setup and let you know. |
One more thing that you can check is if you have installed loki using our documentation and your promtail and loki pods are up and running |
Fission/Kubernetes version
Kubernetes platform (e.g. Google Kubernetes Engine)
MacOS Local Kuberntes
Describe the bug
While following the documentation to add Loki to the monitoring namespace and then adding it as a data source, the data source does not get added.
To Reproduce
Follow the loki integration docs step by step
Expected result
The loki data source gets added
Actual result
Error while adding data source
Additional context
The documentation expects to add the following url as datasource: http://loki.monitoring.svc.local.cluster:3100
Tried multiple iterations:
http://loki-grafana.monitoring.svc.local.cluster:3100
,http://loki-grafana-0.monitoring.svc.local.cluster:3100
,http://10.1.0.94:3100
,http://loki-grafana.monitoring.svc.cluster.local:3100
,http://loki-grafana-0.monitoring.svc.cluster.local:3100
This is some networking issue that hasn't been described in the documentation and according to stackoverflow svc.local.cluster should be svc.cluster.local
The text was updated successfully, but these errors were encountered: