Puppet usage patterns that produce a lot of change can cause the resource_events table to consume a significant amount of disk space. Users that aren't running queries against the events API or using the PE Event Inspector could save disk space and processing time by disabling the storage of these events. We should offer the ability to disable event storage entirely in addition to the event TTL described in PDB-2487.
- When resource-events-ttl is set to zero, resource-events are not stored in the resource events - resource events are not included in the map that is used to make the hash for the resource events
pdb-ext - A test showing that when syncing a report submitted with resource events it syncs to the other PuppetDB and creates a report with the same hash
- When resource-events-ttl is set to zero, resource-events are not stored in the resource events postgres
- resource events are not included in the map that is used to make the hash for the resource events pdb-ext - A test showing that when syncing a report submitted with resource events it syncs to the other PuppetDB and creates a report with the same hash
Added the ability to disable the storage or resource events. If resource-events-ttl is set to zero in the puppetdb config resource events will no longer be stored separately during the storage of a report.