Thomas Casteleyn
Thomas Casteleyn
@srebhan @mstrandboge @skartikey How should the README file for these be changed. What format should be used?
Aha, good idea. Then a second one needs to exist when the plugin only has tracking just for the purpose of keeping track of number of undelivered metrics? (As others...
I came to this issue as well, and it seems it is already possible to specify datasource UID: https://grafana.github.io/grafana-operator/docs/api/#grafanadatasource
Since the operator replaces the var in this directly: ```json "datasource": { "type": "graphite", "uid": "${DS_NAME}" }, ``` You can just enter this: ```yaml datasources: - inputName: DS_NAME datasourceName: 'UID-of-the-datasource'...
Why is there a need to only check for changed inputs?
IMO, this should not be limited to inputs only. For example outputs could also be changing depending on some variables. And being able to stop/start some without touching others would...
What would be needed to support this? I'm willing to create a PR for this.
Would love to use configurable backup name as well. What's the state for this PR?
Just a question: Would it be possible to define different template for each task? e.g. all tasks could use the default format, but a specific task it's own custom format.
What about disable grouping in the notification policy? (Or be able to set a max number over there)