pingcap / pingcap/ticdc

changefeed status monitoring is incorrect

Open
#1,402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/metrics-logging severity/moderate type/bug
Dominant language
Go
Stars
56
Forks
63
Avg merge
2d 20h
Merged PRs (30d)
34

Description

Image
max(ticdc_owner_status{k8s_cluster="$k8s_cluster", tidb_cluster="$tidb_cluster",namespace=~"$namespace", changefeed=~"$changefeed"}) by (namespace,changefeed)

The ticdc_owner_status is not defined in the new arch ticdc. after pause the changefeed, the status is not reported to the prometheus.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the changefeed monitoring query shown in the issue and trace where ticdc_owner_status is defined or emitted in the new-architecture TiCDC. Reproduce the paused-changefeed case and inspect its Prometheus metrics. Done means the paused changefeed status is reported and the monitoring query returns the expected status.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, prometheus
Domain
observability
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.