-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Common system metrics collection #24416
Common system metrics collection #24416
Conversation
…m .h; another small fixes
… "readField" method
Lots of environments already have such monitoring, looks like it worth adding a configuration directive to control these new collectors, and make it OFF by default? Also maybe it worth looking at some existing tools (most popular these days I guess is node exporter) to make these metrics compatible? |
@azat What is the reason for turning these metrics off? The scenario is when a server collected these metrics for a year and at least once these metrics will save a day. |
Perf test Ok (the column has been renamed and the new name does not exist in old version). |
Since in ClickHouse#24416 asynchronous_metrics_update_period_s had been set to 1 and this became annoying.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Collect common system metrics (in
system.asynchronous_metrics
andsystem.asynchronous_metric_log
) about CPU usage, disk usage, memory usage, IO, network, files, load average, CPU frequencies, thermal sensors, EDAC counters, system uptime; also added metrics about the scheduling jitter and the time spent collecting the metrics. It works likeatop
in ClickHouse and allows to get monitoring data even if you have no additional tools installed. This closes #9430.