Skip to content
This repository has been archived by the owner on Mar 22, 2023. It is now read-only.

Alerting Support #19

Open
bubu11e opened this issue Mar 30, 2018 · 6 comments
Open

Alerting Support #19

bubu11e opened this issue Mar 30, 2018 · 6 comments

Comments

@bubu11e
Copy link

bubu11e commented Mar 30, 2018

Will you add the support for the alerting function of Grafana in this datasource ?

@ghost
Copy link

ghost commented Jun 10, 2019

Alerting function is a critical feature for my team.

@miton18
Copy link
Contributor

miton18 commented Jun 19, 2019

Alerting feature have to be done on the Grafana backend (it's the backend which will schedule checks), you can ask Grafana to support Warp10 datasource :-)

@StevenLeRoux
Copy link
Contributor

Alerting is managed as backend queries in Grafana. We need to move the query layer from the frontend to the backend in the plugin, which means a fairly deep rework.

We don't use this feature from Grafana, but still, we will accept contributions.

@KillianH
Copy link

I will be happy to help but I don't know exactly where to begin (the grafana documentation is not really clear about this part)...

@KillianH
Copy link

KillianH commented Oct 22, 2019

Actually there's a backend updated branch for the simple json datasource https://github.com/grafana/simple-json-datasource/tree/backend-updated and also a grafana plugin sdk to write plugins (in alpha). https://github.com/grafana/grafana-plugin-sdk-go

Someone wants to try those with me ? 😁

@Whyrl35
Copy link

Whyrl35 commented Jan 15, 2021

Indeed it could be great to have alerting support for those that run warp10 by their own.

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

No branches or pull requests

5 participants