Exposing cluster topology and status via frontend http api

[sunng87]

What type of enhancement is this?

API improvement

What does the enhancement do?

As mentioned in GreptimeTeam/dashboard#159 , it would be nice to have an overview of cluster status, including:

• how many datanodes, frontends and metas in current cluster
• their address, load and other usage information
• how many clients are connected to current cluster

These information will be reporting to meta via heartbeats, and exposed via frontend HTTP API, say /v1/self/status

Implementation challenges

No response

[SSebo]

Is this issue open for community contributor? @sunng87

[sunng87]

I think we are approaching an alternative solution for this in #2921 and #2931 . You might be interested in one of those tasks.

[sunng87]

I'm closing this because we are going to implement this with sql and table data from information schema.