Skip to content

branch-4.1: [improve](streaming-job) add per-job lag metric to streaming insert jobs #63194#63271

Open
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63194-branch-4.1
Open

branch-4.1: [improve](streaming-job) add per-job lag metric to streaming insert jobs #63194#63271
github-actions[bot] wants to merge 1 commit into
branch-4.1from
auto-pick-63194-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Cherry-picked from #63194

@github-actions github-actions Bot requested a review from yiguolei as a code owner May 15, 2026 01:55
@JNSimba
Copy link
Copy Markdown
Member

JNSimba commented May 19, 2026

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/14) 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 28.57% (4/14) 🎉
Increment coverage report
Complete coverage report

@JNSimba JNSimba closed this May 19, 2026
@JNSimba JNSimba reopened this May 19, 2026
…obs (#63194)

### What problem does this PR solve?

Related PR: #62224 (per-job metrics), #62269 (Lag column)

Problem Summary:

#62224 introduced per-job metrics (`streaming_job_per_job_scanned_rows`,
`_load_bytes`, `_filtered_rows`, `_succeed_task_count`,
`_failed_task_count`) for streaming insert jobs, exposed via `/metrics`
with `job_id`/`job_name` labels for Prometheus.

#62269 later added a `Lag` column to `SHOW JOBS` / `jobs()` TVF that
reports end-to-end CDC delay in seconds, but the value was only exposed
through SQL — there was no corresponding Prometheus metric, so
dashboards/alerting on lag was not possible.

This PR adds `streaming_job_per_job_lag` (unit: `SECONDS`) to the
existing per-job metric set.
@JNSimba JNSimba force-pushed the auto-pick-63194-branch-4.1 branch from 8d2e425 to 7f7b9c2 Compare May 19, 2026 06:03
@JNSimba
Copy link
Copy Markdown
Member

JNSimba commented May 19, 2026

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 0.00% (0/14) 🎉
Increment coverage report
Complete coverage report

@hello-stephen
Copy link
Copy Markdown
Contributor

FE Regression Coverage Report

Increment line coverage 64.29% (9/14) 🎉
Increment coverage report
Complete coverage report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants