You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering how hard it would be to add a proper "API" to telemetry to expose the sort of information requested in #479. The reason being that the data sent to the UI is deliberately fairly minimal/compact (what the UI needs and no more), and also is not an interface we promise to support/not break.
Also, for the benefit of our future selves, having a clear split between "this is what we are sending to populate the UI" and "this is the more nicely structured and actually supported interface for obtaining node information programmatically" would be really valuable.
This API might be some sort of HTTP RESTful thing, or it might be something like JSONRPC over a websocket/http channel.
Let's gather up some of the information that is desirable to access programmatically here, so we can come up with an API to provide it.
The text was updated successfully, but these errors were encountered:
I'm wondering how hard it would be to add a proper "API" to telemetry to expose the sort of information requested in #479. The reason being that the data sent to the UI is deliberately fairly minimal/compact (what the UI needs and no more), and also is not an interface we promise to support/not break.
Also, for the benefit of our future selves, having a clear split between "this is what we are sending to populate the UI" and "this is the more nicely structured and actually supported interface for obtaining node information programmatically" would be really valuable.
This API might be some sort of HTTP RESTful thing, or it might be something like JSONRPC over a websocket/http channel.
Let's gather up some of the information that is desirable to access programmatically here, so we can come up with an API to provide it.
The text was updated successfully, but these errors were encountered: