Skip to content

Telemetry gRPC ingest breaks UI but still is exposed #2355

@golyalpha

Description

@golyalpha

Describe the bug
When ingesting telemetry (on OneUptime Open Source) via the gRPC endpoint of the cluster-internal service, UIs that handle traces tend to break (page goes white and a bad route exception is logged - it seems things like trace IDs are sent to the frontend as bytes, rather than hex-encoded strings)

Tested with Python instrumentation, exporter version 1.39.1

To Reproduce
Steps to reproduce the behavior:

  1. Send traces to OneUptime's Telemetry service via the gRPC endpoint
  2. Try to open traces view, open log details, or set up a traces monitor
  3. After trace data loads the page goes blank

Expected behavior
Either:
Traces from the gRPC endpoint should be transformed so the UI can handle them correctly
The gRPC endpoint should probably not be exposed at all - even via the cluster-internal service.

Desktop (please complete the following information):

  • OS: Win11
  • Browser Brave
  • Version 1.88.130

Deployment Type
Self-hosted

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions