public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Grafana live: Remove experimental language around redis (#107217)

Browse Source
This commit is contained in:
Stephanie Hingtgen
2025-06-27 16:40:13 -07:00
committed by GitHub
parent 0dd9417aa9
commit 5cdc19403a
3 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
conf/defaults.ini
-2
View File
@@ -1887,12 +1887,10 @@ allowed_origins =
# engine defines an HA (high availability) engine to use for Grafana Live. By default no engine used - in
# this case Live features work only on a single Grafana server.
# Available options: "redis".
# Setting ha_engine is an EXPERIMENTAL feature.
ha_engine =
# ha_engine_address sets a connection address for Live HA engine. Depending on engine type address format can differ.
# For now we only support Redis connection address in "host:port" format.
# This option is EXPERIMENTAL.
ha_engine_address = "127.0.0.1:6379"
# ha_engine_password allows setting an optional password to authenticate with the engine
conf/sample.ini
-2
View File
@@ -1824,12 +1824,10 @@ default_datasource_uid =
# engine defines an HA (high availability) engine to use for Grafana Live. By default no engine used - in
# this case Live features work only on a single Grafana server. Available options: "redis".
# Setting ha_engine is an EXPERIMENTAL feature.
;ha_engine =
# ha_engine_address sets a connection address for Live HA engine. Depending on engine type address format can differ.
# For now we only support Redis connection address in "host:port" format.
# This option is EXPERIMENTAL.
;ha_engine_address = "127.0.0.1:6379"
# ha_engine_password allows setting an optional password to authenticate with the engine
docs/sources/setup-grafana/set-up-grafana-live.md
+1 -1
View File
@@ -201,7 +201,7 @@ In a high availability Grafana setup involving several Grafana server instances
- Streaming from Telegraf will deliver data only to clients connected to the same instance which received Telegraf data, active stream cache is not shared between different Grafana instances.
- A separate unidirectional stream between Grafana and backend data source may be opened on different Grafana servers for the same channel.
To bypass these limitations, Grafana v8.1 has an experimental Live HA engine that requires Redis to work.
To bypass these limitations, Grafana has a Live HA engine that requires Redis to work.
### Configure Redis Live engine