Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/puppet/kandra/manifests/prometheus/uwsgi.pp

34 lines
1.1 KiB
ObjectPascal
Raw Normal View History

puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
# @summary Prometheus monitoring of uwsgi servers
#
puppet: Rename puppet/zulip_ops to puppet/kandra. This makes for easier tab-completion, and also is a bit more explicit about the expected consumer.
2024-02-06 21:40:19 +01:00
class kandra::prometheus::uwsgi {
include kandra::prometheus::base
prometheus: Consistently import the base class and supervisor, if needed.
2023-03-30 20:02:42 +02:00
include zulip::supervisor
puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
$version = $zulip::common::versions['uwsgi_exporter']['version']
$dir = "/srv/zulip-uwsgi_exporter-${version}"
$bin = "${dir}/uwsgi_exporter"
puppet: Factor out $::architecture case statement for golang.
2022-02-11 20:37:31 +01:00
puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
zulip::external_dep { 'uwsgi_exporter':
version => $version,
puppet: Factor out $::architecture case statement for golang.
2022-02-11 20:37:31 +01:00
url => "https://github.com/timonwong/uwsgi_exporter/releases/download/v${version}/uwsgi_exporter-${version}.linux-${zulip::common::goarch}.tar.gz",
tarball_prefix => "uwsgi_exporter-${version}.linux-${zulip::common::goarch}",
puppet: Stop relying on "tidy" ordering, which ignores metaparams. The `tidy` parameter is buggy, and ignores all ordering metaparameters. This is fixed in Puppet 7[^1], but it's helpful to resolve it now. Specifically, this fixes bugs with tidy running too early, and deleting the old version of a package before its new version is installed or symlinked, leaving a race condition if anything tries to run the binary in this window. This is mostly not a problem for Supervisor-managed processes, since the binary is already running, and can continue to run if it is tidied out from under the running process. For stand-alone tools like wal-g, which are run frequently by PostgreSQL, this may cause issues if PostgreSQL tries to call them during a puppet run. Remove all complicated uses of tidy, and replace them with an `exec` which does the equivalent. We also generate `file` resources for binaries, making them easier (and clearer) to specify as dependencies. [^1]: https://puppet.atlassian.net/browse/PUP-10688
2024-04-15 20:11:08 +02:00
bin => [$bin],
cleanup_after => [Service[supervisor]],
puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
}
puppet: Rename puppet/zulip_ops to puppet/kandra. This makes for easier tab-completion, and also is a bit more explicit about the expected consumer.
2024-02-06 21:40:19 +01:00
kandra::firewall_allow { 'uwsgi_exporter': port => '9238' }
puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
file { "${zulip::common::supervisor_conf_dir}/prometheus_uwsgi_exporter.conf":
ensure => file,
require => [
User[zulip],
Package[supervisor],
puppet: Stop relying on "tidy" ordering, which ignores metaparams. The `tidy` parameter is buggy, and ignores all ordering metaparameters. This is fixed in Puppet 7[^1], but it's helpful to resolve it now. Specifically, this fixes bugs with tidy running too early, and deleting the old version of a package before its new version is installed or symlinked, leaving a race condition if anything tries to run the binary in this window. This is mostly not a problem for Supervisor-managed processes, since the binary is already running, and can continue to run if it is tidied out from under the running process. For stand-alone tools like wal-g, which are run frequently by PostgreSQL, this may cause issues if PostgreSQL tries to call them during a puppet run. Remove all complicated uses of tidy, and replace them with an `exec` which does the equivalent. We also generate `file` resources for binaries, making them easier (and clearer) to specify as dependencies. [^1]: https://puppet.atlassian.net/browse/PUP-10688
2024-04-15 20:11:08 +02:00
File[$bin],
puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
],
owner => 'root',
group => 'root',
mode => '0644',
puppet: Rename puppet/zulip_ops to puppet/kandra. This makes for easier tab-completion, and also is a bit more explicit about the expected consumer.
2024-02-06 21:40:19 +01:00
content => template('kandra/supervisor/conf.d/prometheus_uwsgi_exporter.conf.template.erb'),
puppet: Add a uwsgi exporter for monitoring. This allows investigation of how many workers are busy, and to track "harikari" terminations.
2022-01-01 05:00:17 +01:00
notify => Service[supervisor],
}
}