Skip to content
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 Logcli is not working #1468

Closed
AnandPalani92 opened this issue Jan 6, 2020 · 4 comments
Closed

Loki Logcli is not working #1468

AnandPalani92 opened this issue Jan 6, 2020 · 4 comments

Comments

@AnandPalani92
Copy link

Describe the bug
I have tried the loki logcli to access the container logs on kubernetes and itsn't not working. I used to following way as per the loki documentation. Environment vars exposed as mentioned.
$ export GRAFANA_ADDR=https://test.grafanadomain.com
$ export GRAFANA_USERNAME=admin
$ export GRAFANA_PASSWORD=admin123

After exposed the environment vars and i got following error.

Capture1

Expected behavior
logcli labels analytics
https://monitoring-dev.example.com//loki/api/v1/label/analytics/values
Error doing request: readObjectStart: expect { or n, but found <, error found in #1 byte of ...|

Environment:

  • Infrastructure: Aws EKS environment
  • Deployment tool: helm charts

Screenshots, Promtail config, or terminal output
image

@sandeepsukhani
Copy link
Contributor

Can you please try hitting that URL directly using a browser and see what HTML is being returned? I suspect some other component is erroring out and the request is not even reaching Loki.

@AnandPalani92
Copy link
Author

AnandPalani92 commented Jan 7, 2020 via email

@sandeepsukhani
Copy link
Contributor

I think the issue is with the url that is set in GRAFANA_ADDR. It should be pointing to loki server, not grafana since logcli is meant to talk to loki server directly. Can you please give a try after updating it?

@AnandPalani92
Copy link
Author

Yes. Its working now. as per the Docs i just given the Grafana url

Thanks for your prompt response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants