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

Plugin can not be health checked #164

Closed
juaniyyoo opened this issue Feb 16, 2022 · 2 comments
Closed

Plugin can not be health checked #164

juaniyyoo opened this issue Feb 16, 2022 · 2 comments
Labels
type/bug Unexpected behavior or a feature is broken

Comments

@juaniyyoo
Copy link

Hello,

The plugin is not working and can not be health checked.

I tried installing and uninstalling it in grafana GUI and grafana-cli. However it keeps sending back "Plugin unvailable" message with a 503 return code from https://[HOST]/api/datasources/[id]/health. Aside, plugins such as prometheus work.

I am using the default grafana/grafana latest docker image.
Grafana cli version is : Grafana CLI version 8.3.6

Here are grafana logs :

t=2022-02-16T19:52:01+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/api/live/ws status=0 remote_addr=[my local address] time_ms=2 size=0 referer=
t=2022-02-16T19:56:26+0000 lvl=eror msg="Plugin unavailable" logger=context userId=1 orgId=1 uname=admin error="plugin unavailable" remote_addr=[my local address]

Browser logs :

WebSocket connection to 'ws://[SERVER ADDRESS]:3000/api/live/ws' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED

Everything is working up for other plugins.

Would you have any idea about it ?

@marcusolsson
Copy link
Contributor

Hm. Plugin unavailable together with a 503 typically means that the plugin has crashed. Do you have any idea of how I could reproduce this on my end? Are you using a public URL? Or are you reading a local file?

@zoltanbedi
Copy link
Member

I'm going to close this issue as no answer was given.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Unexpected behavior or a feature is broken
Projects
None yet
Development

No branches or pull requests

4 participants