[TASK] Display the node hardware data (will need to fetch from telemetry likely)

[drewstone]

Overview

Fetch node data from Telemetry. It's entirely possible that this can't be done super easily. Telemetry might not provide identifiable data about a specific node but rather provide network wide data.

[drewstone]

Verify if this is possible and very quickly move on from it if it is not (put it on hold). Ask on Stackexchange as well how to query against the telemetry if that's the only place. Otherwise, we want to add a feature to the gadget to expose hardware specs and focus on the gadget's machines CC @Tjemmmic @tbraun96

[Tjemmmic]

A relevant PR: https://github.com/paritytech/substrate-telemetry/pull/519

[vutuanlinh2k2]

Oh-hold this for now.

These were what I have researched on:

• Polkadot Telemetry gets the data of nodes by listening to events of a Websocket, the URL of it was auto-generated with Docker (not sure how at the moment). Their code for getting the URL is here and for handling the data is here
• A problem here is that even if we can get the data, the data will be for the whole network, and we have to filter that large amount of data for each validator
• Tested listening for ws://127.0.0.1:9944/feed for local Tangle but no event was emitted

Related links that can be used later:

• https://github.com/paritytech/substrate-telemetry/blob/7bf2925/frontend/src/common/feed.ts
• https://github.com/paritytech/substrate-telemetry/blob/7bf2925a238963c597be63e5d460723bd06c5a22/frontend/src/Connection.ts#L152
• https://github.com/paritytech/substrate-telemetry/blob/7bf2925a238963c597be63e5d460723bd06c5a22/frontend/src/Connection.ts#L56

[github-actions[bot]]

This issue is stale because it has been open for 60 days with no activity.