You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, Kafka metric computing is just Kafka record, but record can be unpacked. We should compute unpacked data.
And, Kafka 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
the similar issue is: #5762
What happened
Now, Kafka metric computing is just Kafka record, but record can be unpacked. We should compute unpacked data.
And, Kafka 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
the similar issue is: #5762
How to reproduce
just test inlongmsg format
Environment
No response
InLong version
master
InLong Component
InLong Sort
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: