Open luisj1983 opened 2 years ago
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
Thanks @luisj1983 this is a great suggestion.
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
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.
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.
How can one obtain the node_id
s known to a netdata server via console / commandline?
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
Importance
must have
Value proposition
1. 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