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 health check failed since upgrade to Grafana 10 #438

Closed
jelmokri opened this issue Jun 27, 2023 · 9 comments
Closed

Plugin health check failed since upgrade to Grafana 10 #438

jelmokri opened this issue Jun 27, 2023 · 9 comments

Comments

@jelmokri
Copy link

Hello,

it seems the plugin is not compatible with Grafana 10.
Since the upgrade, I have the following error when I save the datasource :
"Plugin health check failed"

Is there a way to fix without downgrade grafana version ?

Thanks for your help.

@jelmokri jelmokri added datasource/ClickHouse type/bug Something isn't working labels Jun 27, 2023
@mshustov
Copy link
Collaborator

@jelmokri, what plugin version do you use? v3.1.0 is compatible with v10 https://github.com/grafana/clickhouse-datasource/blob/main/CHANGELOG.md

@jelmokri
Copy link
Author

Hello, I use the 3.1.0 version of the plugin with grafana 10.0.1

When I save the datasource , I have the error above and so all the panels depending of this datasource not work anymore

@IsStatic
Copy link

IsStatic commented Jul 4, 2023

mark,me too

@aangelisc
Copy link
Contributor

Hi @jelmokri, @grafana/observability-metrics
I've tested 3.1.0 against Grafana 10 today and I can successfully connect to a ClickHouse datasource. Do you have any more details on the errors you're seeing?

@itsmylife
Copy link

@aangelisc I think we (@grafana/observability-metrics) tagged by mistake? Do you need anything specific from our side?

@aangelisc
Copy link
Contributor

@itsmylife I'm not sure why you were tagged but yep that's a mistake! Don't worry nothing needed from you 😊

@jelmokri
Copy link
Author

You can close the issue.

I have fixed it by using full FQDN in Server address of the datasource configuration

@mshustov
Copy link
Collaborator

I have fixed it by using full FQDN in Server address of the datasource configuration

@jelmokri what server address and port did you use before? We can implement a proper validation

@jelmokri
Copy link
Author

before : server:port
after: FQDN:port

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

No branches or pull requests

5 participants