Alerting: Introduce proper feature toggles for common state history backend combinations (#65650)

* Alerting: Introduce proper feature toggles for common state history backend combinations (#65497)

* define 3 feature toggles for rollout phases

* Pass feature toggles along

* Implement first feature toggle

* Try a different strategy with fall-throughs to specific configurations

* Apply toggle overrides once outside of backend composition

* Emit log messages when we coerce backends

* Run code generator for feature toggle files

* Improve wording in flag descs

* Re-run generator

* Use code-generated constants instead of plain strings

* Use converted enum values rather than strings for pre-parsing

(cherry picked from commit b2abb63286)

* Remove generated file that is only present in future versions
This commit is contained in:
Alexander Weaver
2023-03-30 14:29:43 -05:00
committed by GitHub
parent 66e3f8dc23
commit e9d53761fb
6 changed files with 82 additions and 1 deletions
@@ -100,6 +100,9 @@ Alpha features might be changed or removed without prior notice.
| `logsContextDatasourceUi` | Allow datasource to provide custom UI for context view |
| `prometheusMetricEncyclopedia` | Replaces the Prometheus query builder metric select option with a paginated and filterable component |
| `influxdbBackendMigration` | Query InfluxDB InfluxQL without the proxy |
| `alertStateHistoryLokiSecondary` | Enable Grafana to write alert state history to an external Loki instance in addition to Grafana annotations. |
| `alertStateHistoryLokiPrimary` | Enable a remote Loki instance as the primary source for state history reads. |
| `alertStateHistoryLokiOnly` | Disable Grafana alerts from emitting annotations when a remote Loki instance is available. |
## Development feature toggles