Skip to content

[Bug]: [UI] System Architecture Graph: Edge label text is obscured/clipped on self-referencing nodes #3500

@singhvibhanshu

Description

@singhvibhanshu

What happened?

I encountered a visual bug in the System Architecture tab (DAG view) where the request count label for a self-referencing edge is partially obscured by the service node icon.

Specifically, the edge loop for the frontend service has a request count of 228, but it renders visually as 28 (or similar), with the leading digit clipped or hidden behind the node circle.

Steps to reproduce

  1. Open the System Architecture tab in the Jaeger UI.
  2. Locate a service node that has a self-referencing dependency (a loop where the service calls itself).
  3. Observe the request count label on the loop edge.
  4. Notice that the text label overlaps with the node icon, making the number difficult or impossible to read correctly.

Expected behavior

The edge label text should be positioned clearly outside the node's boundary or have a higher z-index/background to ensure it is fully legible. It should not clip behind the service icon.

Relevant log output

Screenshot

I inspected the element in the browser DevTools to confirm the data is present but visually hidden.

  • Element: <text> inside the plexus-Digraph--SvgEdgesLayer.
  • Value: 228
  • Observation: The x and y coordinates for the text seem to place it too close to the node center for this specific graph layout.
Image

Image

Additional context

Actual Behavior
The text label overlaps with the node. In my specific case:

  • Actual Value: 228 (verified via DOM inspector).
  • Rendered Value: Looks like 28 because the first 2 is obscured.

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

Linux

Deployment model

Docker

Deployment configs

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions