Skip to content

Change to Sensor from PollingSensor for SQS Sensor #90

Open
@grepory

Description

@grepory

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions