[feat](job) add per-job routine load metrics#63576
Open
sollhui wants to merge 1 commit into
Open
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
0c17b7d to
17b51b9
Compare
Contributor
Author
|
run buildall |
Contributor
TPC-H: Total hot run time: 31618 ms |
Contributor
TPC-DS: Total hot run time: 173292 ms |
Contributor
FE Regression Coverage ReportIncrement line coverage |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Problem Summary:
Before this change, FE only exposed aggregate routine load metrics, such as total loaded rows, error rows, received bytes, task execution time, progress, lag, and aborted task count across all routine load jobs. These metrics were useful for observing the whole FE, but they could not identify which routine load job contributed to a spike, lag, or abnormal error/task count.
This change adds per-job routine load metrics. Each metric is exported with
job_idandjob_namelabels, so users can inspect the status of a single routine load job from the FE metrics endpoint.The new metrics are:
doris_fe_routine_load_per_job_total_rowsdoris_fe_routine_load_per_job_error_rowsdoris_fe_routine_load_per_job_received_bytesdoris_fe_routine_load_per_job_task_execute_timedoris_fe_routine_load_per_job_task_execute_countdoris_fe_routine_load_per_job_progressdoris_fe_routine_load_per_job_lagdoris_fe_routine_load_per_job_abort_task_numExample query from FE metrics endpoint:
Example Prometheus query:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)