Wishlist: automatic DB pruning

[Peter Sabaini]

The maasserver_event table seems to grow unbounded over time.

For long running installations this can be problematic:

a) disk space consumption

b) more cycles needed to keep table + indices updated

Example, we're running an installation since 2017 and the maas event table plus indices use ~6.5Gb. Otoh it seems unlikely that 2 year old machine events would bring much value.

It would be great if MAAS could either do automatic pruning of events older than X days, or provide a script or similar to prune or archive events manually

(cloned from Bug #1830365)

[Adam Beeman (abeeman)]

I've found larger environments need maasserver_event to be truncated after a while; loading the Machines page takes longer and longer as the this table grows.

[João Pedro Seara (jpseara)]

Might be related to bug #1880966 [1]

[1] https://bugs.launchpad.net/maas/+bug/1880966

[Adam Collard (adam-collard)]

This is related to https://bugs.launchpad.net/maas/+bug/1403080 as well, see comments there for some workarounds.

As per the latest comment on that bug, this forms part of a retention policy feature request. This will be picked up as part of MAAS roadmap, no specific implementation date can be given now.

[Jerzy Husakowski (jhusakowski)]

On MAAS feature backlog