-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Task] hertzbeat metrics collector cluster design #1003
Comments
讨论存疑:
|
Discussion in doubt:
|
在监控量不大的情况下,是否保留原来的模式,以简化部署难度?当初就是看着hz不用额外部署agent才用的 |
In the case of a small amount of monitoring, should the original mode be retained to simplify the difficulty of deployment? At the beginning, it was only used when looking at hz without additional deployment of agent |
是的,默认还是会单体 all in one. 设计时也会尽量减少外部组件依赖 |
Yes, the default is still all in one. The design will also minimize external component dependencies |
如果在主 hz中提供webhook來接收其他collector的信息会不会减少对kafka的依赖 |
If webhook is provided in the main hz to receive information from other collectors, will it reduce the dependence on Kafka? |
可以有 把它做成可配置的形式 默认webhook |
It can be made into a configurable form, the default webhook |
感觉这个更像是提供一个控制中心呢😂 |
It feels more like providing a control center😂 |
Description
why collector cluster?
desgin discuss
Task List
No response
The text was updated successfully, but these errors were encountered: