Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

branch-3.0: [improve](routine load) add more metrics to observe the routine load job #48209 #48764

Open
wants to merge 1 commit into
base: branch-3.0
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Mar 6, 2025

Cherry-picked from #48209

…job (#48209)

### What problem does this PR solve?

related #48511

Add more metrics to observe the routine load job:

| Metrics | Module | Description |
| ---------------------------------- | ------ |
------------------------------- |
| routine_load_get_msg_latency | BE | Time to pull a Kafka message |
| routine_load_get_msg_count | BE | Number of times pulling Kafka
messages |
| routine_load_consume_bytes | BE | Total data volume consumed from
Kafka |
| routine_load_consume_rows | BE | Total number of rows consumed from
Kafka |
| routine_load_task_execute_time | FE | Task execution time |
| routine_load_task_execute_count | FE | Task execution count |
| routine_load_get_meta_latency | FE | Delay in obtaining Kafka metadata
|
| routine_load_get_meta_count | FE | Number of times obtaining Kafka
metadata |
| routine_load_get_meta_fail_count | FE | Number of failures in
obtaining metadata |
| routine_load_received_bytes | FE | Total data volume consumed |
| routine_load_received_rows | FE | Total number of rows consumed |
@github-actions github-actions bot requested a review from dataroaring as a code owner March 6, 2025 09:55
@Thearas
Copy link
Contributor

Thearas commented Mar 6, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@dataroaring dataroaring closed this Mar 6, 2025
@dataroaring dataroaring reopened this Mar 6, 2025
@Thearas
Copy link
Contributor

Thearas commented Mar 6, 2025

run buildall

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.

3 participants