-
Notifications
You must be signed in to change notification settings - Fork 121
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
Support Basic Auth for datasource which used BasicAuth for alerts #267
Comments
Im using Docker with a mounted plugin directory. |
could you share your table schema also, could you share results for following command |
error: code = Unknown desc = invalid status code. status: 500 Internal Server Error" changing state to=alerting |
Don't know if it helps but datasource is using basic auth. |
Not sure if this is a heisenbug but I tried it again and this time it worked. Need to investigate it. |
Something else I've found along the way. If you select by you will get following error: |
toStartOfHour it's expected behavior |
Ah ok. Thanks I will. Currently I use (intDiv(toUInt32(CallTime), 3600) * 3600) * 1000 as t. |
maybe "heisenbug" depends of data which returned from your datasource could you check |
Ok, thanks for the hint, I will see if I can find something useful. |
Ok we are lucky and it's not a heisenbug. I can reproduce it. It works now because in the datasource settings I turned the switch on "Use Yandex.Cloud authorization headers" and filled the credentials. Even if you turn of the switch again it will still work. Looking into the code I found this: |
If you delete the credentials for Yandex.Cloud authorization headers you will see the mentioned error again. |
I'm facing the same issue with self hosted clickhouse and basic auth, any news or workaround on the subject? |
@via-justa look to #275 |
I 've met the same problem. But what is this "Use Yandex.Cloud authorization headers" used for? It seems like account of Yandex.Cloud, why does it can solve this problem? In my test environment, I didn't turn this on, but the Alert is OK. |
@xgxshtc it means use authorization method via please read https://clickhouse.tech/docs/en/interfaces/http/ for details |
Thks a lot, it really helped. Now it works. |
So, my story is:
|
@glebsam thanks a lot for workaround ;) |
This issue should be resolved by #314 |
@bmanth60 thank you very much for your great work! |
## Breaking changes * On latest Grafana 7.x releases, template variables SQL queries shall return only scalar types of values, see Altinity/clickhouse-grafana#328 ## Enhancement: * add support Apple M1 ;) * switch to new grafana plugin Golang SDK, thanks to @bmanth60 and @valeriakononenko for help * add BasicAuth support for alerts, see Altinity/clickhouse-grafana#267 ## Fixes: * fix github actions backend build * fix UNION ALL parsing, see Altinity/clickhouse-grafana#319 * fix many issues with alerting * Altinity/clickhouse-grafana#305 * Altinity/clickhouse-grafana#327 * Altinity/clickhouse-grafana#334 * Altinity/clickhouse-grafana#335 Signed-off-by: Eugene Klimov <[email protected]>
## Breaking changes * On latest Grafana 7.x releases, template variables SQL queries shall return only scalar types of values, see Altinity/clickhouse-grafana#328 ## Enhancement: * add support Apple M1 ;) * switch to new grafana plugin Golang SDK, thanks to @bmanth60 and @valeriakononenko for help * add BasicAuth support for alerts, see Altinity/clickhouse-grafana#267 ## Fixes: * fix github actions backend build * fix UNION ALL parsing, see Altinity/clickhouse-grafana#319 * fix many issues with alerting * Altinity/clickhouse-grafana#305 * Altinity/clickhouse-grafana#327 * Altinity/clickhouse-grafana#334 * Altinity/clickhouse-grafana#335 Signed-off-by: Eugene Klimov <[email protected]>
## Breaking changes * On latest Grafana 7.x releases, template variables SQL queries shall return only scalar types of values, see Altinity/clickhouse-grafana#328 ## Enhancement: * add support Apple M1 ;) * switch to new grafana plugin Golang SDK, thanks to @bmanth60 and @valeriakononenko for help * add BasicAuth support for alerts, see Altinity/clickhouse-grafana#267 ## Fixes: * fix github actions backend build * fix UNION ALL parsing, see Altinity/clickhouse-grafana#319 * fix many issues with alerting * Altinity/clickhouse-grafana#305 * Altinity/clickhouse-grafana#327 * Altinity/clickhouse-grafana#334 * Altinity/clickhouse-grafana#335 Signed-off-by: Eugene Klimov <[email protected]>
With Grafana 7.1.1 and latest clickhouse-grafana plugin version 2.0.5 every Alert throws following error:
error:"tsdb.HandleRequest() error rpc error: code = Unknown desc = invalid status code. status: 500 Internal Server Error"
For graphs the datasourse is working normally.
The text was updated successfully, but these errors were encountered: