GitHub puppet-prometheus
Puppet module for prometheus

Repo Checks ( 17 of 24 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Virtuozzolinux
No translation
passed
Supports Latest Virtuozzolinux
No translation
failed
Supports Only Current Debian
No translation
failed
Supports Latest Debian
No translation
passed
Supports Only Current Ubuntu
No translation
failed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Archlinux
No translation
failed
Supports Latest Archlinux
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
passed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

allow specifying services that should start before the exporter daemon
merge-conflicts
needs-work
tests-fail

Pull Request (PR) description

Allow specifying other services that should be started prior to the exporter daemon starting up in systemd. This is to handle situations where you want the service being monitored to be started before the exporter.

This Pull Request (PR) fixes the following issues

N/A (new feature)

Open PR in GitHub
Add parameter user / group for ressource archive
backwards-incompatible
tests-fail
merge-conflicts
feat(daemon): be able to use another systemd-module
enhancement
merge-conflicts
needs-docs
needs-tests
tests-fail

Pull Request (PR) description

  • feat(daemon): be able to use another systemd-module
  • feat(node_exporter): be able to use another systemd-module

This Pull Request (PR) fixes the following issues

n/a

Open PR in GitHub
WIP: Fix for the #434 dependency cycle
tests-fail

Fixes #434

Note: this PR is still Work-In-Progress as I have not tested all edge cases but it does work. Perhaps you have the time to take a look on your side and maybe your will either immediately tell me that is totally wrong or the other way around. I will get back to this when I will have more time.

Open PR in GitHub
blackbox_exporter:modules leaking sensitive info so adding no diff
fix syntax of altermanager::receivers
bug
needs-tests

The "name" block is an object. This actually matches the example in
prometheus::alertmanager's documentation:

```

@param receivers

An array of receivers.

Example (also default):

prometheus::alertmanager::receivers:

- name: 'Admin'

email_configs:

- to: 'root@localhost'

```

I wonder why unit tests didn't catch those...?

Closes: #539

Open PR in GitHub
allow to set env_vars for blackbox exporter
needs-tests
merge-conflicts

Pull Request (PR) description

This PR is intended to allow environment variables to be set for the blackbox exporter.
This can be useful, for example, if you want to use SSL_CERT_FILE.

This Pull Request (PR) fixes the following issues

Fixes #535

Open PR in GitHub
mongodb_exporter: Add acceptance tests
tests-fail
needs-rebase

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
WIP: Add FreeBSD 13 for node_exporter and server

I added some default settings in Data to be working on FreeBSD 13

Open PR in GitHub
Add prometheus node-exporter name for Ubuntu
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Add package prometheus-node-exporter package name for Debian.

This Pull Request (PR) fixes the following issues

Installation on Ubuntu 18.04

Open PR in GitHub
Rename exporters to prometheus::exporter::$EXPORTER
backwards-incompatible
merge-conflicts
tests-fail

This is the result of using sed + rename. Untested, may eat your dog etc.

Open PR in GitHub
Release 12.4.0
merge-conflicts

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
Update default external_labels
backwards-incompatible

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->
The following commit sets external_labels to an empty hash by default. The previous value prevent the use of deep-merge strategy for the key prometheus::global_config when using hiera.

⚠️ This might be a breaking change for some users

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
None

Open PR in GitHub
Add iperf3 exporter

Change-Id: I9e4a0166d789bcc553bfb59f621846339fa8ded4

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

This is to add an iperf3 exporter. Details in https://github.com/edgard/iperf3_exporter

Open PR in GitHub
WIP: data/Debian.yaml, add package- and service-names for Debian-based prometheus-packages
tests-fail
merge-conflicts

Together with #430 this PR adapts the Debian-defaults regarding package- and service-names like they are actually present in Debian. e.g. all exporters are prefixed with prometheus-.

https://packages.debian.org/search?keywords=prometheus&searchon=names&suite=stable&section=all

```bash
user@host:~$ for A in $(apt-cache search prometheus- | awk '{ print $1 }' | xargs); do apt-file show $A 2>&1 | grep -E '(systemd/system)'; done
prometheus-alertmanager: /lib/systemd/system/prometheus-alertmanager.service
prometheus-apache-exporter: /lib/systemd/system/prometheus-apache-exporter.service
prometheus-bind-exporter: /lib/systemd/system/prometheus-bind-exporter.service
prometheus-bird-exporter: /lib/systemd/system/prometheus-bird-exporter.service
prometheus-blackbox-exporter: /lib/systemd/system/prometheus-blackbox-exporter.service
prometheus-haproxy-exporter: /lib/systemd/system/prometheus-haproxy-exporter.service
prometheus-mongodb-exporter: /lib/systemd/system/prometheus-mongodb-exporter.service
prometheus-mysqld-exporter: /lib/systemd/system/prometheus-mysqld-exporter.service
prometheus-nginx-exporter: /lib/systemd/system/prometheus-nginx-exporter.service
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-apt.service
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-apt.timer
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-ipmitool-sensor.service
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-ipmitool-sensor.timer
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-mellanox-hca-temp.service
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-mellanox-hca-temp.timer
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-smartmon.service
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter-smartmon.timer
prometheus-node-exporter: /lib/systemd/system/prometheus-node-exporter.service
prometheus-pgbouncer-exporter: /lib/systemd/system/prometheus-pgbouncer-exporter.service
prometheus-postgres-exporter: /lib/systemd/system/prometheus-postgres-exporter.service
prometheus-process-exporter: /lib/systemd/system/prometheus-process-exporter.service
prometheus-pushgateway: /lib/systemd/system/prometheus-pushgateway.service
prometheus-snmp-exporter: /lib/systemd/system/prometheus-snmp-exporter.service
prometheus-sql-exporter: /lib/systemd/system/prometheus-sql-exporter.service
prometheus-squid-exporter: /lib/systemd/system/prometheus-squid-exporter.service
prometheus-varnish-exporter: /lib/systemd/system/prometheus-varnish-exporter.service
prometheus-xmpp-alerts: /lib/systemd/system/prometheus-xmpp-alerts.service

```

Open PR in GitHub
download_extension: Switch from String to Optional[String[1]]
merge-conflicts

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
add env vars and env file path

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Add envvars and envfile_path variable

This Pull Request (PR) fixes the following issues

This allows Username and password to be passed through the ESUSERNAME and ESPASSWORD environment variables.
Ref: https://github.com/prometheus-community/elasticsearch_exporter/commit/80e25faf48ff6283cfcb9e560e44b0f7b20976ab

Open PR in GitHub
Move the URL releases to their own directory under /opt to create the…
enhancement

Move the URL releases to their own directory under /opt to create the possibility for Puppet to remove old releases that are no longer used.

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

In order to achieve that Puppet can clean up the directory in which Prometheus and the exporters are located, I have created a subdirectory under /opt. This allows Puppet to purge the directory which would lead to unwanted behavior with /opt.

However, this would reinstall all exporters once, which would require one-time manual clean-up. Then you can have that automatically.

So that the change is minimally invasive, I have the whole thing activated via a variable that is deactivated by default.

Please let me know if anything is missing or if my approach does not fit.

This Pull Request (PR) fixes the following issues

Fixes #625

Open PR in GitHub
fix file ownerships
merge-conflicts

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Currently most exporters have weird permissions after being installed (e.g. 3434:3434 ownership). For the exporters installed via daemon, there is already a patch applied, which sets the owner and group to root:0 for the executables, which still leaves files like "LICENSE" etc. with the wrong ownerships. I am adding a patch for all files, replacing the old patch.

This Pull Request (PR) fixes the following issues

Fixes #111

Open PR in GitHub
haproxy_exporter: escape cnf_scrape_uri to avoid malformed strings
bug

Pull Request (PR) description

Hello, this PR changes the way cnfscrapeuri is being escaped in manifests/haproxy_exporter.pp to avoid malformed string like the one being described in Issue #600.

This Pull Request (PR) fixes the following issues

Fixes #600

Open PR in GitHub
Support time_intervals with alertmanager >= 0.24.0

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

Adds time_intervals parameter to alertmanager that is supported with 0.24.0 and newer. This will replace mute_time_intervals which is now deprecated.

https://github.com/prometheus/alertmanager/releases/tag/v0.24.0

Also fixed the usage examples for mute_time_intervals to be the correct data structures.

Open PR in GitHub
added ability for config file content to be specified for process_exp…
merge-conflicts
needs-work

…orter

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
add `timeout_stop` to control systemd `TimeoutStopSec`
enhancement
needs-rebase
merge-conflicts

Pull Request (PR) description

With larger WAL segments, prometheus fails to write
a new checkpoint in TimeoutStopSec time:


Oct 03 15:13:37 prometheus prometheus[2452]: level=info ts=2020-10-03T15:13:37.751Z caller=checkpoint.go:96 component=tsdb msg="Creating checkpoint" from_segment=85417 to_segment=85677 mint
Oct 03 15:15:06 prometheus systemd[1]: prometheus.service: State 'stop-sigterm' timed out. Killing.
Oct 03 15:15:06 prometheus systemd[1]: prometheus.service: Killing process 2452 (prometheus) with signal SIGKILL.
Oct 03 15:15:06 prometheus systemd[1]: prometheus.service: Main process exited, code=killed, status=9/KILL
Oct 03 15:15:06 prometheus systemd[1]: prometheus.service: Failed with result 'timeout'.
Oct 03 15:15:06 prometheus systemd[1]: Stopped Prometheus Monitoring framework.

This change adds a new parameter to define TimeoutStopSec
for prometheus.service.

This Pull Request (PR) fixes the following issues

No issue previously created.

The required systemd unitfile overwrite could have been made locally as well - but as I suppose that others could also face similar issues, I decided to implement the parameter directly.

Open PR in GitHub