netdata-cloud icon indicating copy to clipboard operation
netdata-cloud copied to clipboard

[Feat]: Make sharing node id and space id easy

Open luisj1983 opened this issue 3 years ago • 6 comments

Problem

I was recently troubleshooting an issue with Netdata and one of your team asked for the Space ID and NodeID of the affected agent. I had to ask about the Space ID because it’s merely an ID and not a GUID and so it’s the space name; and yet the node ID is something like a GUID (don’t know if it’s global to Netdata or to my instance of data).

In any case it wasn’t obvious to find this information and it’s important for troubleshooting.

Description

  1. I’d like to suggest that the Space ID is added to the dialog which comes up when you select the cog/setting icon for that workspace/War Room; and the Node ID should come up when you click the “Select Node Information” button for a node (which should be trivial as it’s in the JSON output).
  2. Some documentation covering this as a Google search only turned up bug reports which ask for the values and don’t mention how to get them.

Importance

must have

Value proposition

If you want to make troubleshooting easier you need this sort of basic info to be easily available to sysadmin types and not require people to parse through ever lengthening URLs :)

Proposed implementation

No response

luisj1983 avatar Jun 30 '22 16:06 luisj1983

This issue has been mentioned on the Netdata Community Forums. There might be relevant details there:

https://community.netdata.cloud/t/feature-request-node-id-and-space-id-in-web-gui/3044/4

netdata-community-bot avatar Jun 30 '22 17:06 netdata-community-bot

Thanks @luisj1983 this is a great suggestion.

shyamvalsan avatar Jul 01 '22 08:07 shyamvalsan

I think there sort of is at least a workaround here: https://community.netdata.cloud/t/feature-request-node-id-and-space-id-in-web-gui/3044/5?u=andrewm4894

andrewm4894 avatar Jul 01 '22 09:07 andrewm4894

Yup, that's why I figured it was a small change :grin: And parsing through a bunch of XML is a poor user experience, hence the RFC. Plus, to be pedantic (sorry, not sorry), the XML mentions an "ID" field and not a "Node ID" field. It's not obvious whether that "ID" value is context-dependent or not because it's just an "ID" and that could mean anything. As I said, a doc change is the absolute minimum as it took me time and fruitless Googling to figure it out. It's such a simple thing causing unnecessary friction; but it seems like a low-effort UI change to simply expose information that's already there.

luisj1983 avatar Jul 01 '22 12:07 luisj1983

I really don't understand, why are we asking for these instead of the URL when they look at a single node view? It contains the unique space slug (not the name) + the node id. We just need to never request these two again.

cakrit avatar Jul 01 '22 14:07 cakrit

How can one obtain the node_ids known to a netdata server via console / commandline?

luckman212 avatar Jun 22 '24 18:06 luckman212