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

[Bug][Sort] The computing of Pulsar source metric was wrong #5762

Closed
2 tasks done
gong opened this issue Sep 1, 2022 · 0 comments · Fixed by #5763
Closed
2 tasks done

[Bug][Sort] The computing of Pulsar source metric was wrong #5762

gong opened this issue Sep 1, 2022 · 0 comments · Fixed by #5763
Assignees
Labels
component/sort type/bug Something is wrong
Milestone

Comments

@gong
Copy link
Contributor

gong commented Sep 1, 2022

What happened

Now, pulsar metric computing is just pulsar record, but record can be unpacked. We should compute unpacked data.
And, pulsar metric name is not right. We expect metric name is flink_taskmanager_job_task_operator_groupId_streamId_nodeId_numRecordsIn, but metric name is flink_taskmanager_job_task_operator_user_groupId_streamId_nodeId_numRecordsIn

What you expected to happen

metric result is right and metric name is right

How to reproduce

just test inlongmsg format

Environment

No response

InLong version

master

InLong Component

InLong Sort

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@gong gong added the type/bug Something is wrong label Sep 1, 2022
@healchow healchow added this to the 1.4.0 milestone Sep 1, 2022
@healchow healchow changed the title [Bug][Sort] Fix pulsar source metric computing [Bug][Sort] The computing of Pulsar source metric was wrong Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/sort type/bug Something is wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants