[GH-ISSUE #17001] issue: RedisInstrumentor does not support Redis Sentinel #18133

New Issue

GiteaMirror · 2026-04-20T00:14:52-05:00

GiteaMirror commented

2026-04-20 00:14:52 -05:00

Originally created by @Salamastik on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17001

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Other

Open WebUI Version

0.6.18

Ollama Version (if applicable)

No response

Operating System

debian gnu/linux 12

Browser (if applicable)

111.0.5563.65

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

OpenTelemetry should collect Redis metrics and traces normally, whether Redis is running in Cluster or Sentinel mode.

Actual Behavior

When configuring OpenWebUI to use Redis Sentinel instead of Redis Cluster, OpenTelemetry starts producing warnings. The same OTEL setup works fine with Redis Cluster.
This indicates that OTEL currently lacks proper support for Redis Sentinel connections.
With Redis Sentinel → OTEL logs continuous warnings (likely due to missing attributes in instrumentations.py).

Steps to Reproduce

When using Redis Sentinel the RedisInstrumentor from opentelemetry-instrumentation-redis fails and produces repeated WARN logs.

OpenWebUI version: 0.6.18 Deployment: Helm (7.6.0)
Installed Redis using the Bitnami Helm chart:

Chart: bitnami/redis-sentinel 21.1.6

Image: bitnami/redis-sentinel:8.0.1-debian-12.r1

Updated OpenWebUI configuration to connect via Sentinel (REDIS_SENTINEL_HOST, REDIS_SENTINEL_PORT, REDIS_SENTINEL_SERVICE, REDIS_URL).

OpenWebUI successfully connected to Redis Sentinel.

However, OpenTelemetry started generating warnings that were not present before (when using Redis Cluster).

Tried using OTEL environment variables such as OTEL_PYTHON_DISABLED_INSTRUMENTATIONS=redis, but the warnings persisted.

Logs & Screenshots

WARNING opentelemetry.attributes:_clean_attribute:111 invalid type NoneType for attribute 'db.ip' value. Expected one of ['bool', 'str', 'bytes', 'float'] or a sequence of those types.

Additional Information

Please add official OpenTelemetry support for Redis Sentinel in OpenWebUI.
This will ensure consistent observability for setups that rely on Sentinel for high availability, just like with Redis Cluster.

Originally created by @Salamastik on GitHub (Aug 28, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17001 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Other ### Open WebUI Version 0.6.18 ### Ollama Version (if applicable) _No response_ ### Operating System debian gnu/linux 12 ### Browser (if applicable) 111.0.5563.65 ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior OpenTelemetry should collect Redis metrics and traces normally, whether Redis is running in Cluster or Sentinel mode. ### Actual Behavior When configuring OpenWebUI to use Redis Sentinel instead of Redis Cluster, OpenTelemetry starts producing warnings. The same OTEL setup works fine with Redis Cluster. This indicates that OTEL currently lacks proper support for Redis Sentinel connections. With Redis Sentinel → OTEL logs continuous warnings (likely due to missing attributes in instrumentations.py). ### Steps to Reproduce When using Redis Sentinel the RedisInstrumentor from opentelemetry-instrumentation-redis fails and produces repeated WARN logs. OpenWebUI version: 0.6.18 Deployment: Helm (7.6.0) Installed Redis using the Bitnami Helm chart: Chart: bitnami/redis-sentinel 21.1.6 Image: bitnami/redis-sentinel:8.0.1-debian-12.r1 Updated OpenWebUI configuration to connect via Sentinel (REDIS_SENTINEL_HOST, REDIS_SENTINEL_PORT, REDIS_SENTINEL_SERVICE, REDIS_URL). OpenWebUI successfully connected to Redis Sentinel. However, OpenTelemetry started generating warnings that were not present before (when using Redis Cluster). Tried using OTEL environment variables such as OTEL_PYTHON_DISABLED_INSTRUMENTATIONS=redis, but the warnings persisted. ### Logs & Screenshots WARNING opentelemetry.attributes:_clean_attribute:111 invalid type NoneType for attribute 'db.ip' value. Expected one of ['bool', 'str', 'bytes', 'float'] or a sequence of those types. ### Additional Information Please add official OpenTelemetry support for Redis Sentinel in OpenWebUI. This will ensure consistent observability for setups that rely on Sentinel for high availability, just like with Redis Cluster.

GiteaMirror added the bug label 2026-04-20 00:14:52 -05:00

GiteaMirror closed this issue

2026-04-20 00:15:01 -05:00

GiteaMirror commented

2026-04-20 00:15:07 -05:00

@tjbck commented on GitHub (Aug 28, 2025):

PR welcome.

@tjbck commented on GitHub (Aug 28, 2025): PR welcome.

GiteaMirror referenced this issue

2026-04-20 00:44:16 -05:00

[GH-ISSUE #18133] issue: 0.6.33 - Focused Retrieval mode doesn't work #18507

GiteaMirror referenced this issue