improve observability for procedure #3999
Labels
A-metasrv
Involves code in the meta server
C-feature
Category Features
C-user-experience
Category User Experience
help wanted
Extra attention is needed
What problem does the new feature solve?
Currently we are not able to check the state of each procedure, how long it takes, which resources it keeps, or which state it at. It's hard to debug or verify things related to one specific procedure.
This ticket proposes to improve the observability of procedures, by exposing the above things somewhere. Like an HTTP API or a table in information_schema.
Useful links
procedure state
greptimedb/src/common/procedure/src/procedure.rs
Lines 301 to 315 in 1b58622
acquiring locks
greptimedb/src/common/procedure/src/local/runner.rs
Lines 115 to 125 in 5303537
implement cluster_info table in information_schema feat: adds information_schema cluster_info table #3832
What does the feature do?
ProcedureState::Running
to contain aString
. This string shows a procedure's current stage.Implementation challenges
No response
The text was updated successfully, but these errors were encountered: