-
Notifications
You must be signed in to change notification settings - Fork 83
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 Datasources aren't possible #114
Comments
Possible solution:
If it's not possible to get if the datasource type exists currently (at least not without cli access which should be a nogo for this module!) then I would pledge to just create it as provided. If the implement a way we can update the module. |
maybe an approach to store the data source config as api exportable json config, much like wizzy does, and is being done for dashboards, this way it becomes very flexible and removes some of the magic from the ansible modue. As custom and new data sources (jaeger example of unsupported by module) all need different settings, even es 7 does now. As well as new features such as custom http headers. This way maintenance and duplication needed here would be less. Could even support vars in the json, by simply running the json through the template engine, before applying to the grafana api. |
{ |
I would create a PR to implement json generic api plugin usage. Please let me know if this would supported from your side ? |
Any progress on this? We had started using this module but when we were unable to create a Prometheus Alertmanager datasource, it kind of put us at a roadblock. |
SUMMARY
Currently the possible datasources are hardcoded so ds from plugins like
camptocamp-prometheus-alertmanager-datasource
aren't possible.ISSUE TYPE
COMPONENT NAME
grafana_datasource
The text was updated successfully, but these errors were encountered: