Repository navigation
Change to Sensor from PollingSensor for SQS Sensor #90
Description
Right now, the PollingSensor caps at 10 messages per second due to the API limit for maximum messages in a transaction and the minimum polling rate of 1 Hz.
We have modified the SQS sensor locally to be a continuously running Sensor that does its own polling loop instead of a scheduled poll as we have to handle 30+ messages per second. Would this be a welcomed upstream contribution?
Activity
Kami commentedon Dec 18, 2019
Yeah, the contribution would be more than welcome.
For backward compatibility and similar reasons, it would probably be good to add it as a separate sensor though.
grepory commentedon Dec 18, 2019
That makes sense to me. Thanks!