Allowing for deployment of alertmanager directly from binary, almost identical to how its being done in the default prometheus recipe. The 'source' deployment is left as default, but I found the binary more useful for deploying the beta versions https://github.com/prometheus/alertmanager/releases .
Note moving away from 0.0.4 into the beta versions involves significant changes to the config (for starters, it's .yml), I am doing that by changing ['prometheus']['alermanager']['config_template_name'] and ...["config.file"] and running on the parent recipe:
template "/tmp/alertmanager.yml" do
source 'alertmanager.yml.erb'
mode 0644
end
Note also that alertmanager needs to run as root (['prometheus']['user'] and ['prometheus']['group'] must be root) otherwise has some issues with permissions.
Allowing for deployment of alertmanager directly from binary, almost identical to how its being done in the default prometheus recipe. The 'source' deployment is left as default, but I found the binary more useful for deploying the beta versions https://github.com/prometheus/alertmanager/releases .
Note moving away from 0.0.4 into the beta versions involves significant changes to the config (for starters, it's .yml), I am doing that by changing ['prometheus']['alermanager']['config_template_name'] and ...["config.file"] and running on the parent recipe: template "/tmp/alertmanager.yml" do source 'alertmanager.yml.erb' mode 0644 end
Note also that alertmanager needs to run as root (['prometheus']['user'] and ['prometheus']['group'] must be root) otherwise has some issues with permissions.