I've set up a PR with the changes needed in the termini in order to stop sending reports if one of the resource events hits the upper limit for the `resource_events_resource_timestamp_xxxxxxxxz` index. An error will be printed with all the details related to the resource that is oversized and caused the error. Also, I noticed that currently the resource event is not saved if the error is thrown on insert, but the the resource is still saved in the database. |