-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable reports by default #9461
base: main
Are you sure you want to change the base?
Conversation
Can one of the admins verify this patch? |
if reports were also automatically purged after 30 days, then I'd argue for it to be left on. But as things are, |
Documentation would also need an update: https://www.puppet.com/docs/puppet/latest/report.html |
I couldn't find the source for this documentation, but it should remove the mention that |
filebuckets suffered from the same unbounded growth. Changing to
The source for reference docs is in puppet now, so this will be easy to fix. See puppet/rakelib/generate_references.rake Lines 54 to 58 in 7f67aef
|
My suggestion to fix the documentation page: diff --git a/references/report.md b/references/report.md
index dba027d1f7..80ef9218a3 100644
--- a/references/report.md
+++ b/references/report.md
@@ -39,12 +39,15 @@ log
Send all received logs to the local log destinations. Usually
the log destination is syslog.
+none
+----
+Discard all reports received. This is the default handler when the `reports`
+setting is unset.
+
store
-----
Store the yaml report on disk. Each host sends its report as a YAML dump
and this just stores the file on disk, in the `reportdir` directory.
These files collect quickly -- one every half hour -- so it is a good idea
-to perform some maintenance on them if you use this report (it's the only
-default report).
-
+to perform some maintenance on them if you use this report. |
The default value for this goes all the way back to when it was introduced in 566bf78. I'd argue it a bad default, because it just writes files without any clean up process in place. That only causes hard disks to fill up. Having reports should be an opt in feature, where they make a careful choice. PuppetDB is an obvious recommended option but not one that can be relied on by default.
576b709
to
148e599
Compare
Something like this? |
In terms of whether to ship this in Puppet 8 or 9, my preference is to ship this as an update in Puppet 8. The consequence of the current default is likely to lead to filesystems filling up and breaking the system, as we've seen from bug reports in Debian (eg. #1078911) If it's delayed to Puppet 9 we're sure to backport the change to 8 in Debian. We're also seriously considering backporting this to 7, in Debian stable. |
As much as I agree that Related, we had the same problem with filebuckets and we changed the default behavior in 8e9657f first released in puppet 7.0 |
The default value for this goes all the way back to when it was introduced in 566bf78. I'd argue it a bad default, because it just writes files without any clean up process in place. That only causes hard disks to fill up.
Having reports should be an opt in feature, where they make a careful choice. PuppetDB is an obvious recommended option but not one that can be relied on by default.
This came up because of a discussion in Debian. I never thought about this because I always set up Foreman as reports and don't rely on it, but this to me is the sanest default.