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.

Sign up for GitHub

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

Jump to bottom

[LabelBot] Alarming #30

Open
marcoabreu opened this issue Nov 7, 2018 · 0 comments
Open

[LabelBot] Alarming #30

marcoabreu opened this issue Nov 7, 2018 · 0 comments

Comments

@marcoabreu
Copy link
Contributor

With the last deployment, we noticed that we didn't really know where to look for while investigating an issue. In the end, it was the SQS queue that was not being consumed. Afterwards, we had exceptions being thrown #23 that were not bubbled up.

It would be good if there were some monitors/alarms that could be attached that trigger if the SQS queue gets too full (flood), messages don't get consumed (outage) or if there is an exception during execution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marcoabreu