Why you need it?
Though we already have metrics service and prometheus exporter, there is still one more work to do in terms of observability, i.e. a visualizer. Nowadays, users have to maintain a self-made grafana panel to observe Seata metrics.
How it could be?
I propose to implement an out-of-box grafana panel for users to quickly get hands on. And we can integrate the grafana panel to Seata console, to make Seata console a one-stop control plane for Seata transaction.
The grafana panel should be like something in this blog post .
Other related information
How do you guys think?
6条答案
按热度按时间pdsfdshx1#
In my opinion
First, we need to sort out all the metrics, similar to https://pulsar.apache.org/docs/3.1.x/reference-metrics/ .
Then, provide a Grafana JSON configuration template that can be submitted to https://grafana.com/grafana/dashboards/ for maintenance.
toe950272#
Agree with @leizhiyuan proposal
6gpjuf903#
In my opinion
First, we need to sort out all the metrics, similar to https://pulsar.apache.org/docs/3.1.x/reference-metrics/ .
Then, provide a Grafana JSON configuration template that can be submitted to https://grafana.com/grafana/dashboards/ for maintenance.
Agreed. Also, the first step has already been done, since all supported metrics can be found in this doc .
9rygscc14#
#4878 The client side has some future metrics
myss37ts5#
A followup here. A demo grafana panel that integrates current metrics:
dm7nw8vv6#
A followup here. A demo grafana panel that integrates current metrics:
could you share this grafana json config please?