Skip to content

ui: Gossip graph debug page #27652

@bdarnell

Description

@bdarnell

It's sometimes useful to look at a graph of gossip connections to identify partitions. The edges in the gossip graph are available on a per-node basis in the logs:

[n10] gossip status (ok, 9 nodes)
gossip client (2/3 cur/max conns)
  12: n12:26257 (34m1s: infos 5764/7020 sent/received, bytes 2049681B/2854441B sent/received)
  4: n4:26257 (34m1s: infos 1733/33091 sent/received, bytes 791770B/4877590B sent/received)
gossip server (2/3 cur/max conns, infos 76313/46057 sent/received, bytes 16145538B/10178190B sent/received)
  7: n7:26257 (32m20s)
  8: n8:26257 (30m55s)

We can aggregate this information across all nodes to produce a graph like this:

image

I'd like to have such a graph in the debug pages (perhaps the /reports/network page)

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-webuiTriage label for DB Console (fka admin UI) issues. Add this if nothing else is clear.C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)X-staleno-issue-activity

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions