This is probably more related to lavinmq itself and putting some level of data collection and monitoring around it. In the UI, lavinmq has Publish Rate and ACK Rate values per queue. Tracking that number over a given time with publish/ack should present a number that lets you know if your system is under or over provisioned. My only thought with this is, if tj_lavin can give you the data easily enough, it might be easier to put this data into the app your building for easier data collection.
Currently the easiest way to get this sort of information is to use the prometheus interface that lavinmq has and put that into something like influxdb.
This is probably more related to lavinmq itself and putting some level of data collection and monitoring around it. In the UI, lavinmq has
Publish RateandACK Ratevalues per queue. Tracking that number over a given time withpublish/ackshould present a number that lets you know if your system is under or over provisioned. My only thought with this is, if tj_lavin can give you the data easily enough, it might be easier to put this data into the app your building for easier data collection.Currently the easiest way to get this sort of information is to use the prometheus interface that lavinmq has and put that into something like influxdb.