metrics,grafana: show changefeed downstream type (#4251)

[ti-chi-bot]

This is an automated cherry-pick of #4251

What problem does this PR solve?

Issue Number: close #4250

What is changed and how it works?

• Add a constant-gauge metric ticdc_owner_changefeed_downstream_info{namespace|keyspace_name, changefeed, downstream_type} 1 to expose downstream type per changefeed.
• Derive downstream_type from the sink-uri scheme and normalize it to a small stable set (e.g. mysql+ssl -> mysql, pulsar+https -> pulsar, gs -> gcs, azure -> azblob).
• Add a filterable table panel in the Changefeed section of the TiCDC Grafana dashboard to show each changefeed's downstream type.

Check List

Tests

• Unit test
• Manual test

Questions

Will it cause performance regression or break compatibility?

No. This PR only adds an additive metric and dashboard panel, and the per-changefeed metric update is on the same 5s loop as existing changefeed metrics.

Do you need to update user documentation, design documentation or monitoring documentation?

Monitoring dashboard is updated.

Release note

Add a changefeed downstream type metric and show it in the TiCDC Grafana Changefeed section.

Summary by CodeRabbit

• New Features

  • Expose changefeed downstream type and TiDB confirmation as new metrics; add Grafana table panels showing downstream types.

• Bug Fixes

  • Safer handling and cleanup when changefeed info is missing to prevent nil-related issues and stale metric labels.

• Behavior

  • Metrics now update and remove downstream-type and TiDB-confirmation labels when feeds change or are removed/shutdown.

• Tests

  • Added unit tests validating downstream-type extraction from sink URIs.

[ti-chi-bot]

@wlwilliamx This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

[ti-chi-bot]

This cherry pick PR is for a release branch and has not yet been approved by triage owners.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick:

1. It must be LGTMed and approved by the reviewers firstly.
2. For pull requests to TiDB-x branches, it must have no failed tests.
3. AFTER it has lgtm and approved labels, please wait for the cherry-pick merging approval from triage owners.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[ti-chi-bot]

@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c5ce3681-b9f6-4034-b69e-3771fedc093c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wlwilliamx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [wlwilliamx]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[wlwilliamx]

/unhold

[wlwilliamx]

/test all