github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 19:38:46 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #16183] issue: OTEL Metrics export not working with http protocol #17818

New Issue
Closed
opened 2026-04-19 23:42:33 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 23:42:33 -05:00
Owner
Copy Link

Originally created by @JARZcorp on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16183

Check Existing Issues

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

Installation Method

Git Clone

Open WebUI Version

v0.6.18

Ollama Version (if applicable)

No response

Operating System

Ubuntu

Browser (if applicable)

No response

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

When setting ENABLE_OTEL_METRICS to true, Metrics should be exported to the given OTLP Endpoint. By default the grpc protocol is used. If I set OTEL_OTLP_SPAN_EXPORTER to http the Traces as well as Metrics should be exported via http.

Actual Behavior

  1. Traces are exported using http but OW is still trying to export the Metrics using gRPC.

Steps to Reproduce

Set the following env variables in OW 0.6.18:
ENABLE_OTEL = true
OTEL_EXPORTER_OTLP_ENDPOINT = your endpoint
ENABLE_OTEL_METRICS = true
OTEL_EXPORTER_OTLP_INSECURE = true
OTEL_OTLP_SPAN_EXPORTER = http
OTEL_EXPORTER_OTLP_PROTOCOL = http/protobuf (just to be 100% sure that http is used, not sure if needed)
OTEL_BASIC_AUTH_USERNAME = xx
OTEL_BASIC_AUTH_PASSWORD = xx

Logs & Screenshots

2025-07-31T11:47:02.3027495Z stdout F 2025-07-31 11:47:02.302 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 2s. - {}
2025-07-31T11:47:04.3035723Z stdout F 2025-07-31 11:47:04.303 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 4s. - {}
2025-07-31T11:47:08.3044032Z stdout F 2025-07-31 11:47:08.304 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 8s. - {}
2025-07-31T11:47:16.3052524Z stdout F 2025-07-31 11:47:16.304 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 16s. - {}
2025-07-31T11:47:22.3839667Z stdout F 2025-07-31 11:47:22.383 | WARNING |

Additional Information

Besides the bug that http is not working for OTEL metrics. Would it be possible/make sense to have two different OTEL ENDPOINT env variables, one for traces and one for metrics?

Originally created by @JARZcorp on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16183 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.18 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu ### Browser (if applicable) _No response_ ### 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 When setting ENABLE_OTEL_METRICS to true, Metrics should be exported to the given OTLP Endpoint. By default the grpc protocol is used. If I set OTEL_OTLP_SPAN_EXPORTER to http the Traces as well as Metrics should be exported via http. ### Actual Behavior 1. Traces are exported using http but OW is still trying to export the Metrics using gRPC. ### Steps to Reproduce Set the following env variables in OW 0.6.18: ENABLE_OTEL = true OTEL_EXPORTER_OTLP_ENDPOINT = your endpoint ENABLE_OTEL_METRICS = true OTEL_EXPORTER_OTLP_INSECURE = true OTEL_OTLP_SPAN_EXPORTER = http OTEL_EXPORTER_OTLP_PROTOCOL = http/protobuf (just to be 100% sure that http is used, not sure if needed) OTEL_BASIC_AUTH_USERNAME = xx OTEL_BASIC_AUTH_PASSWORD = xx ### Logs & Screenshots 2025-07-31T11:47:02.3027495Z stdout F 2025-07-31 11:47:02.302 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 2s. - {} 2025-07-31T11:47:04.3035723Z stdout F 2025-07-31 11:47:04.303 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 4s. - {} 2025-07-31T11:47:08.3044032Z stdout F 2025-07-31 11:47:08.304 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 8s. - {} 2025-07-31T11:47:16.3052524Z stdout F 2025-07-31 11:47:16.304 | WARNING | opentelemetry.exporter.otlp.proto.grpc.exporter:_export:328 - Transient error StatusCode.UNAVAILABLE encountered while exporting metrics to otlp-gateway-prod-eu-north-0.grafana.net, retrying in 16s. - {} 2025-07-31T11:47:22.3839667Z stdout F 2025-07-31 11:47:22.383 | WARNING | ### Additional Information Besides the bug that http is not working for OTEL metrics. Would it be possible/make sense to have two different OTEL ENDPOINT env variables, one for traces and one for metrics?
GiteaMirror added the bug label 2026-04-19 23:42:33 -05:00
GiteaMirror commented 2026-04-19 23:42:34 -05:00
Author
Owner
Copy Link

@JARZcorp commented on GitHub (Aug 11, 2025):

Thanks for fixing it so fast, great job!

<!-- gh-comment-id:3173520829 --> @JARZcorp commented on GitHub (Aug 11, 2025): Thanks for fixing it so fast, great job!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17818
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?