* docs: clarify clustered gc env tunables
* docs: use suggested wording
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
---------
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
* docs: object versioning, lifecycle rule best practices
* docs: trim whitespace
* docs: include appinstance configuration
* docs: update gc env var wording
Co-authored-by: Fraser Savage <fraser@savage.engineer>
* chore: use suggested wording
Co-authored-by: Dom <dom@itsallbroken.com>
* docs: dedicated mention of versioning recommendation
The versioning really depends on an organisation's backups/DR strategy.
I've pulled this more inline with how the lifecylce of the ingested data
can be managed through the garbage-collector.
* docs: wording
* docs: use scenario wording suggestion
Co-authored-by: Dom <dom@itsallbroken.com>
* docs: use suggested extension for gc service
Co-authored-by: Dom <dom@itsallbroken.com>
* docs: no versioning suggestion
Co-authored-by: Dom <dom@itsallbroken.com>
* docs: hint requirements for retention
Co-authored-by: Dom <dom@itsallbroken.com>
* docs: mention object store sizing with lower cutoff
* docs: add warning for 3h cutoff
* suggested edits to the clustered ingest lifecycle guide (#5427)
* docs: use suggestion for configurable cutoff floor
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
---------
Co-authored-by: Fraser Savage <fraser@savage.engineer>
Co-authored-by: Dom <dom@itsallbroken.com>
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
Jack