Datasource does not support alerting queries

[SerhiiAksiutin]

Hi,

I am trying to set up an alert for Hipchat (Load test room) using Grafana + Logz io (Quota View panel)

On alert tab in Grafana I am getting "The datasource does not support alerting queries" and when I try to test the rule getting this error:

firing:true
state:"alerting"
conditionEvals:" = true"
timeMs:"3.983ms"
error:"tsdb.HandleRequest() error Could not find executor for data source type: logzio"\

The alert doesn't appear to work because of this. But if I pause it and then resume I will get desired notification in hipchat with the error (because of "If execution error or timeout":"set alerting state" rule)

Source: https://logz.io/blog/grafana-integration/ https://logz.io/blog/enhancing-account-utilization/

[eeddaann]

I encountered the same issue and found a kludge solution - not recommended but better than nothing.. tl;dr: It actually overrides elasticsearch's built-in datasource (which supports alerting) to send logzio's header and it works like a charm - so no need for this datasource.

• Search in Grafana's sources the expression: t,method (I found it in grafana-5.3.0/public/build/5.770fad3a626c70250d5f.js)
• Inject the token like t,headers : {"X-API-TOKEN" : "XXXX"},method
• save the file
• create elasticsearch datasource with the url of logzio (https://api.logz.io/v1/elasticsearch) Some background:
• The alerting engine in grafana is in the backend of grafana - that's what makes the alerting not flexible when it comes to plugins
• behind the scenes this solution "merge" datasource.ts in this repo to datasource.ts in Grafana's repo So a cleaner solution would be to edit this file in Grafana's sources and build Grafana. (It still dirty but anything is cleaner then the solution above)

[SerhiiAksiutin]

Btw, I have contacted Logz.io support for the matter. They have created a future request without ETA. Future request ID is... Actually they didn't provide with one.

[eeddaann]

As I mentioned it depends on Grafana's back-end so for now Logz.io's guys can't really solve it from their end. I tried to find in Grafana's code how Elastic's plugin "talks" to the backend - If this plugin could use the same interface it would be great, but i suspect that it based on the plugin id. that's why I decided to change Elastic's plugin as a quick and dirty workaround.