Skip to content

Conversation

ArthurWrong
Copy link

  1. According to FLIP-33, I replace tpsMetric and outTps with numRecordsInPerSecond and numRecordsOutPerSecond, and replace their counter with numRecordsIn and numRecordsOut at the same time.
  2. Additionally, numRecordsIn, numRecordsOut, numRecordsInPerSecond, numRecordsOutPerSecond, these four metrics can be monitored on aliyun vvp.

@lizhimins
Copy link
Member

lizhimins commented Mar 27, 2024

Thanks for your contributions! Can you rebase to last main branch.

@ArthurWrong ArthurWrong force-pushed the feature_new_metrics branch 3 times, most recently from 7f0a13a to d2278cf Compare March 28, 2024 09:48
@ArthurWrong ArthurWrong force-pushed the feature_new_metrics branch from d2278cf to 12d8922 Compare March 29, 2024 08:00
@ArthurWrong
Copy link
Author

Thanks for your contributions! Can you rebase to last main branch.

Done.

@ArthurWrong ArthurWrong requested a review from humkum April 2, 2024 08:04
@ArthurWrong
Copy link
Author

@lizhimins @humkum Can we review the code and merge it into the main branch?

tchivs added a commit to tchivs/rocketmq-flink that referenced this pull request Jul 8, 2024
According to FLIP-33, I replace tpsMetric and outTps with numRecordsInPerSecond and numRecordsOutPerSecond, and replace their counter with numRecordsIn and numRecordsOut at the same time.
Additionally, numRecordsIn, numRecordsOut, numRecordsInPerSecond, numRecordsOutPerSecond, these four metrics can be monitored on aliyun vvp.
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