SQS queue with long-polling (just a little-modified default driver with additional parameter)
This checker slows down its own execution because it needs to write and extract job which is not the desired behaviour, which in long polling have some worst ranges for this idea.
Also, I get Return-Path: <health@example.com> in my debug log.
At all, pushing and pulling an actual job to and from the queue is not a good solution because of its invasive behaviour.
Maybe a good solution is to use underlined drivers to check the ability to write and read queue, not performing actual actions.
Given the case:
Return-Path: <health@example.com>in my debug log.At all, pushing and pulling an actual job to and from the queue is not a good solution because of its invasive behaviour. Maybe a good solution is to use underlined drivers to check the ability to write and read queue, not performing actual actions.