Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQS alarms #74

Open
gclitheroe opened this issue Aug 1, 2017 · 1 comment
Open

SQS alarms #74

gclitheroe opened this issue Aug 1, 2017 · 1 comment
Assignees

Comments

@gclitheroe
Copy link

There are SQS queues for archive upload notification messaging. This includes dead letter queues. We need to decide what (if anything) to alarm on and where to send the notification in alarm state.

Typical alarm states that are worth notifying for are:

  • any messages on the dead letter queue (dlq). These could not be processed for some reason and after a small number of delivery attempts are moved to the dlq. I have had issues with alarms on dlq sitting in an "insufficient data state" because nothing is happening.
  • messages backing up on a main messaging queue which can mean the consumer has stopped or is not keeping up for some reason.

@quiffman @ozym @nbalfour - it would be good to have some discussion about what to do then we can get this ticket to a ready state.

@gclitheroe
Copy link
Author

This will no longer be relevant when ram cache pkgs etc are used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants