cockroachdb / cockroachdb/cockroach

dbconsole: link to "nodes" from statement activity confuses KV nodes and SQL instances under multitenancy

Open
#103,441 0 comments 0 reactions 0 assignees View on GitHub
A-cluster-observability C-bug T-observability
Dominant language
Go
Stars
32.5k
Forks
4.1k
PR merge metrics
PR metrics pending

Description

**Describe the problem**

I created a 3-node cluster with 5 SQL instances running in separate processes. I also _restarted_ the SQL instances once to ensure they use fresh instance IDs.

So my node IDs are n1,n2,n3.
The SQL instance IDs are 19,20,21,22,23

When I navigate to DB Console for my SQL activities, then navigate to one of the query fingerprints, I see the query was running on "Nodes: N20,N21,N22".

Two problems:

- It's somewhat unclear what the word "nodes" refers to.
- The hyperlink from the text "N20" in this example links to `/nodes/20`, which is an invalid URL. The `/nodes` URLs refer to KV nodes, not SQL instances, and there is no KV node with ID 20 in this example.

**Expected behavior**

- We should choose which words refer to which "kind" of node.
- The hyperlink from SQL insights should link to a page that displays details about SQL instances, not KV nodes.

**Example in a test cluster**
![image](https://github.com/cockroachdb/cockroach/assets/642886/1df3f6e0-eae5-43ba-b4f9-17d767847c4e)

Jira issue: CRDB-28003

Contributor guide

Open the contributing guide

Research direction

Reproduce the DB Console path from SQL activities to a query fingerprint and inspect the “Nodes” labels and links shown there. Trace the SQL insights link target and confirm that the wording distinguishes KV nodes from SQL instances; done means the link is valid and opens SQL instance details.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.