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
So this role can install prometheus from a binary tarball on GitHub (which I feel is a questionable practice, but that's another issue). In our environments, we prefer packages vetted by third parties, namely for auto-upgrades and so on, so we rely on Debian packages.
It's possible to completely skip the install with prometheus_skip_install, but then the role will crash with:
now some of those are due to the role's entries not being sorted the same way (if at all, actually), but some are real issues. Restart=always (or, for that matter, even =on-failure) in particular, is dangerous, see https://bugs.debian.org/1022724
There should be a way to leave all of that stuff alone and focus on configuring the package instead...
The text was updated successfully, but these errors were encountered:
anarcat
added a commit
to anarcat/ansible-prometheus
that referenced
this issue
Sep 27, 2023
So this role can install prometheus from a binary tarball on GitHub (which I feel is a questionable practice, but that's another issue). In our environments, we prefer packages vetted by third parties, namely for auto-upgrades and so on, so we rely on Debian packages.
It's possible to completely skip the install with
prometheus_skip_install
, but then the role will crash with:That's because promtool is in
/usr/bin/promtool
and not/usr/local/bin/promtool
as expected...There's all sorts of issues like this around the package. For example, the
prometheus.service
unit file is overridden, poorly IMHO:now some of those are due to the role's entries not being sorted the same way (if at all, actually), but some are real issues.
Restart=always
(or, for that matter, even=on-failure
) in particular, is dangerous, see https://bugs.debian.org/1022724There should be a way to leave all of that stuff alone and focus on configuring the package instead...
The text was updated successfully, but these errors were encountered: