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.

Sign up for GitHub

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

Jump to bottom

Server resource monitoring for dm components #1501

Open
glkappe opened this issue Jul 27, 2021 · 1 comment
Open

Server resource monitoring for dm components #1501

glkappe opened this issue Jul 27, 2021 · 1 comment
Labels
component/dm Issues about the tiup-dm component type/question Categorizes issue as related to a question.

Comments

@glkappe
Copy link
Contributor

glkappe commented Jul 27, 2021

We need to add server monitoring to dm-worker and dm master to check whether there are server resource bottlenecks in each component of dm in high concurrency scenarios
@glkappe glkappe added the type/bug Categorizes issue as related to a bug. label Jul 27, 2021
@AstroProfundis AstroProfundis mentioned this issue Jul 28, 2021
Merged
@AstroProfundis
Copy link
Contributor

It's possible to deploy monitoring agents with tiup-dm, they are disabled and will not be deployed by default. However, setting an monitored section in the topology on deploy time with ports of both node_exporter and blackbox_exporter will enable the deployment of them.

@AstroProfundis AstroProfundis added component/dm Issues about the tiup-dm component type/question Categorizes issue as related to a question. and removed type/bug Categorizes issue as related to a bug. labels Jul 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/dm Issues about the tiup-dm component type/question Categorizes issue as related to a question.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AstroProfundis @glkappe