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

[Improve]Optimize the collection and output of TubeMQ metrics #2173

Closed
5 tasks done
gosonzhang opened this issue Jan 17, 2022 · 1 comment
Closed
5 tasks done

[Improve]Optimize the collection and output of TubeMQ metrics #2173

gosonzhang opened this issue Jan 17, 2022 · 1 comment
Assignees
Labels
component/tubemq stage/stale Issues or PRs that had no activity for a long time type/improve

Comments

@gosonzhang
Copy link
Contributor

gosonzhang commented Jan 17, 2022

Description

The current implementation of TubeMQ indicators is still not good enough, mainly:

  1. The client has no indicator output;
  2. There is no histogram data output for the statistics of time consumption;
  3. The performance of the implementation is not good enough

Next, I prepare to build against these points.

InLong Component

InLong TubeMQ

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stage/stale Issues or PRs that had no activity for a long time label Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/tubemq stage/stale Issues or PRs that had no activity for a long time type/improve
Projects
None yet
Development

No branches or pull requests

2 participants