@@ -3094,6 +3094,20 @@ for alerting rules. We already have that for scrape targets, but that
doesn't seem to be an issue. It did feel, however, critical for the
more important alerting rules to have a single source of truth.
### PuppetDB integration
Prometheus 2.31 and later [added support for PuppetDB service
discovery](https://github.com/prometheus/prometheus/commit/8920024323ad8fef353ec2fc495894f8748f0687), through the [`puppetdb_sd_config` parameter](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#puppetdb_sd_config). The
[sample configuration file](https://github.com/prometheus/prometheus/blob/release-2.34/documentation/examples/prometheus-puppetdb.yml) shows a bit what's possible.
This approach was [considered during the bookworm upgrade](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40675) but
ultimately rejected because it introduces a dependency on PuppetDB,
which becomes a possible single point of failure for the monitoring
system.
We also have a lot of code in Puppet to handle the exported resources
necessary for this, and it would take a lot of work to convert over.
### Mobile notifications
Like [others][] we do not intend on having on-call rotation yet, and
