You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we decided, we need an optional collector in our node_exporter, it appears the node_exporter.pp creates systemd startup config which is not compatible with node_exporter 0.14.0, which is the default in the current module
Should we upgrade default node_exporter version to 0.15.2 ?
Affected Puppet, Ruby, OS and module versions/distributions
When we decided, we need an optional collector in our node_exporter, it appears the node_exporter.pp creates systemd startup config which is not compatible with node_exporter 0.14.0, which is the default in the current module
Should we upgrade default node_exporter version to 0.15.2 ?
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
in hiera:
What are you seeing
our systemd config is generated like:
this causes node_exporter not to run,
to be installed, but crases after starting, upon investigating i found the error when i started alertmanager by hand.
What behaviour did you expect instead
a running node_exporter
Output log
journalctl:
The text was updated successfully, but these errors were encountered: