-
Notifications
You must be signed in to change notification settings - Fork 26
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
Monitoring epic, Oct 2017 … Sep 2018 #226
Comments
dockerd monitoring has at least one metric that sounds interesting: |
That's impossible with node_exporter 0.16.0 as soon as there are no metrics exported that can express that event. Seems, unreleased version of the node_exporter has alike features, but it's not in "stable" release yet. But frequent restarters are not "active" services so it's probably okay.
node_systemd_units in node_exporter=0.16.0 shows that and also exports meta-self-test Exporting systemd metrics should be done carefully as most of units are useless ( |
I also commented in #220, but posting it here too: https://www.robustperception.io/alerting-on-crash-loops-with-prometheus This does require that the to-be-monitored process uses some prometheus aware library. This is the case for gorush. |
I'll be releasing a new node_exporter with the systemd restarts metric in the next week or so. |
@hellais I would love to see it done in a more generic way as gorush is just a single service out of dozen. That's why I aimed for systemd & docker metrics. |
@darkk IMO, directly instrumenting is extremely valuable. Even just adding the default Prometheus client_golang for example gives you a number of process metrics, including Go internals, process CPU, RSS, etc. It also gives you the standard Prometheus |
For some reason many hosts had no
|
This ticket tracks enhancements to OONI infra monitoring through Oct 2017 … Sep 2018.
hellais-nas
backup) -- d6ba8fcThe text was updated successfully, but these errors were encountered: