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

Proposed new feature, alert when AWS service is down #1255

Closed
trivisonno opened this issue Jun 13, 2023 · 2 comments
Closed

Proposed new feature, alert when AWS service is down #1255

trivisonno opened this issue Jun 13, 2023 · 2 comments

Comments

@trivisonno
Copy link

Not a bug report.

I tried this afternoon to use certain zappa features (tail, update) and received unfamiliar errors.
botocore.errorfactory.ServiceException: An error occurred (ServiceException) when calling the UpdateFunctionCode operation (reached max retries: 4): An error occurred and the request cannot be processed.

I tried researching the error message but wasn't finding any good advice. Thankfully I checked https://health.aws.amazon.com/health/status and discovered that Lambda and API Gateway was having issues. Everything is working fine now, it was entirely an AWS service issue.

I'm not sure how this could be executed, but maybe with some errors it would be worthwhile for zappa to check if AWS is reporting any issues with the resources zappa commonly uses, and report that somehow in error messages? It would've saved me a lot of time and headaches today. Then again, I'm just an amateur programmer.

@monkut
Copy link
Collaborator

monkut commented Aug 14, 2023

Since zappa is mainly a "lambda" based service, it may be difficult to provide an alert that lambda is down if your lambda is not running.

Alarms can be configured in AWS, which may resolve your issue.

@monkut
Copy link
Collaborator

monkut commented Aug 16, 2023

Not clear how this could be handled, and considered out-of-scope for zappa.

closing.

@monkut monkut closed this as completed Aug 16, 2023
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

2 participants