- Jan 11, 2025
-
-
anarcat authored
-
- Jan 10, 2025
-
-
Jérôme Charaoui authored
-
Jérôme Charaoui authored
-
Jérôme Charaoui authored
-
Jérôme Charaoui authored
-
- Jan 08, 2025
-
-
anarcat authored
Adding an explicit token name makes it easier for people to find it again.
-
- Jan 07, 2025
-
-
lelutin authored
I feel like this is not complete, but I jotted down what I knew.
-
- Dec 20, 2024
- Dec 19, 2024
-
-
lelutin authored
The alert was added during phase A of the migration to prometheus but I had not written anything about how to handle those situations.
-
lelutin authored
This goes with the new alert for this condition.
-
zen authored
-
zen authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
lelutin authored
surely not exhaustive, but what I could think of off the top of my head.
-
- Dec 18, 2024
- Dec 17, 2024
-
-
anarcat authored
-
- Dec 16, 2024
-
-
anarcat authored
-
Jérôme Charaoui authored
this updates the puppet control repo proposal to account for the fact that the repository would track an environment as opposed to /etc/puppet altogether it also adds to the proposal renaming hiera -> data, site-modules -> site and adding "legacy" to the environment modulepath which would contain all modules which still need to be either published as a public module or transformed into a profile note that while I've tried to retain consistency with "step 0" of publishing our puppet code, I don't think we should maintain this goal, let alone keep it as the very first step before everything else
-
- Dec 12, 2024
-
-
anarcat authored
Closes: team#41937
-
- Dec 11, 2024
-
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
anarcat authored
-
Jérôme Charaoui authored
-
Jérôme Charaoui authored
We should have better docs about how we monitor Puppet server and agents with Prometheus...
-
Jérôme Charaoui authored
-