system table for source health status

[neverchanje]

Is your feature request related to a problem? Please describe.

It's very common that the source is connectible but somehow just not consumable.
In this case, we need a interface to see what's going on rather than checking the system logs.
Even as a system admin of RisingWave, I would feel frustrating to check the logs, not to mention the users.

Describe the solution you'd like

Either adding the extra information to rw_sources or introducing a new system table called rw_source_status will be fine to me.

• name: text
• error_message: text
• status: 'healthy' | 'unhealthy'
• last_check_ts: timestamptz

Describe alternatives you've considered

No response

Additional context

No response

[BugenZhao]

Just to clarify, source is not a physical concept until #16003 get completed. It's possible that one source executor encounters failure, while another executor for the same source (in another streaming job) is still healthy.

[st1page]

Just to clarify, source is not a physical concept until #16003 get completed. It's possible that one source executor encounters failure, while another executor for the same source (in another streaming job) is still healthy.

Yes, and since shared source needs to implement the backfill operator for each kind of source. We must have some kinds of sources that don't implement shared source for a long time. so the system table's item must be a physical source.