metrics: add mv id/name to backpressure

risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.

https://go.risingwave.com/slack

Apache License 2.0

7.07k stars 582 forks source link

metrics: add mv id/name to backpressure #17994

Open xxchan opened 3 months ago

xxchan commented 3 months ago

related #13481

Currently the granularity is fragment level. It's not easy to tell "what particular MV is causing the increased barrier"

fuyufjh commented 1 month ago

I think https://github.com/risingwavelabs/risingwave/issues/13481 can fulfill this more or less. Shall we close this?

xxchan commented 1 month ago

Indeed. But it needs access to kernel dashboard, which is more troublesome than Grafana. How do you think? 🤔

fuyufjh commented 1 month ago

Agree, this is major drawback of the kernel dashboard.

Back to this topic, +1 for making an MV-level backpressure in the Grafana board, as long as the complexity is acceptable. Let's take an attempt.