[MXS-3851] Show more KafkaCDC router statistics on GUI Created: 2021-11-04 Updated: 2023-12-04 Resolved: 2023-12-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cdc, maxgui |
| Affects Version/s: | None |
| Fix Version/s: | 24.02.0 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Naresh Chandra | Assignee: | Duong Thien Ly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | MXS-SPRINT-193 | ||||||||
| Description |
|
Add a new feature like show KafkaCDC router status by showing with below details. It will be helpful what is happening on the KafkaCDC router from the Primary node or Galera Node. If possible, we can add more related to KafkaCDC then it would be better experience to the user. |
| Comments |
| Comment by Duong Thien Ly [ 2023-10-23 ] |
|
naresh.chandra@copart.com |
| Comment by markus makela [ 2023-10-23 ] |
Please clarify what is meant by tables and schema are currently being replicating from Primary/Galera cluster. The KafkaCDC converts a stream of events so there's only one table being processed at a time and the table may be different for every event. Additionally, the table creation and update dates are better retrieved from the database as that's where the information related to their creation is.
What exactly does this mean? The KafkaCDC service does not store any data on disk and the only thing it stores is a few kilobytes of metadata per table. |
| Comment by Naresh Chandra [ 2023-11-14 ] |
|
Duong/Markus, Sorry for the delay in response. I have missed this to update due to some priority works. If there is a feasibility implement this feature otherwise show only information whichever is possible. |