The rate limiter used to prevent central crashing due to index reports being added to the queue faster than they are processed sets the bucket size to 5, which means that if more than 5 VMs send a report at the approximate same time all the rest are dropped. This is a UX challenge that can be addressed by using a bigger bucket size, which carries a higher risk of central crashing if a too-big bucket is used.

This user story aims to find a value that provides a better UX and whose risk we are comfortable with.