Mysql is backend DB. And there is two points to review:
1. Deadlocks themselfs. Events table has more then 9 million rows, houskeeper is running and here it's an example:
2. Storage period for internal events is configured to 1 day, but there is also alot of unsupported items. So houskeeper will not delete ones that are in problem state (still unsupported). It might make sense to review internal event storage. It is even possible to remove the generation of recovery events for internal data elements for the sake of being able to delete them after a set period (1day)?
In case of impossibility to get rid of unsupported data elements - it is more important to be able to control the size of the event tables than to be able to notify about the item (trigger\rule) status change to supported
At least this requires the note in the documentation.