-
Notifications
You must be signed in to change notification settings - Fork 11
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
Make node_exporters.enable_collectors configurable #127
Comments
One exporter that is currently required is ntp exporter. Right now on clouds using COS only (w/o cos-proxy i.e. new k8s, kf or managed apps) we are missing ntp monitoring. |
Scope for this will be limited to adding ntp exporter as part of the default list of exporters. |
It should not be enabled by default. We often relate grafana-agent to containers and for containers ntp exporter have no value. It should be configurable. At least separate option for ntp exporter. But It's better to make additional exporters configurable. Because I we could make use of another exporters like bcache, conntrack, presssure, nvme and mdadm |
Is the idea to somehow augment the list here?
How would you propose implement this @err404r? |
Enhancement Proposal
There are many useful exporters, which could be very useful.
Currently it looks like this options is hardcoded, but this need to be changed:
Potentially we have a 3 sources for this value:
Obviously each exporter should has corresponding list of alerts, but this is something for the future.
For now it would be cool to make it configurable, so we could enable collectors manually and add custom rules through cos-configurator.
The text was updated successfully, but these errors were encountered: