fix(dx_evidence_graph): coalesce node identity to pod→service→IP (don't collapse empty-pod peers)#70
Open
entlein wants to merge 1 commit into
Conversation
…peers don't collapse Edges whose peer is not a pod (k8s API server, external/IP endpoints, consulted sockets) carry an empty requestor_pod/responder_pod. The Graph widget keyed on *_pod alone, so EVERY such edge collapsed into one bogus "" node — visually merging unrelated peers (the API server, every distinct remote IP) into one. Coalesce node identity to pod, else service, else IP (the same idiom net_flow_graph uses: px.select(src=='', src_ip, src)) and point the adjacencyList from/to at the coalesced columns. Now each distinct peer is its own node. Validated live (px run, forensic_db): control-plane → k8s-apiserver; the 5 consulted sockets → 5 distinct IPs (10.43.143.34, 10.42.0.1, ::1, 127.0.0.1, 10.42.0.43) instead of one merged node. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
dx_evidence_graphGraph widget keys nodes onrequestor_pod/responder_pod. Edges whose peer is not a pod — the k8s API server (responder_service), external/IP endpoints, the new consulted-socket edges (responder_ip) — have an empty*_pod, so they ALL collapse into a single bogus""node, merging unrelated peers.Fix: coalesce node identity to pod → service → IP (the same idiom
net_flow_graphuses,px.select(src==, src_ip, src)), and pointadjacencyList.fromColumn/toColumnat the coalescedrequestor/respondercolumns. Raw*_pod/*_service/*_ipare still returned for hover.Validated live (
px runagainstforensic_db):control-plane → k8s-apiserver; the 5 consulted sockets resolve to 5 distinct IPs (10.43.143.34,10.42.0.1,::1,127.0.0.1,10.42.0.43) instead of one merged node.Pairs with entlein/dx#87 (the consulted-evidence edges, which is what surfaced the empty-pod collapse).
🤖 Generated with Claude Code