-
Notifications
You must be signed in to change notification settings - Fork 26
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
Setup Cloudwatch Logging and Alarms #61
Comments
Health checks would be good to have |
I have enabled cloudwatch alarms for just this status check failure, for now. |
This happened while I have shell access today. Looks like a memory leak. Disk
Memory:
Top Output:
Both the java processes (prod and dev backend services) are taking 2GB+ each, which should not be happening. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Aim: Avoid downtime by proactive monitoring.
Cloudwatch in free tier allows 10 custom alarms and metrics. It can be used for this.
If cpu/memory/(disk utilisation) goes above a threshold for the , alert send to dev team. If for some reason the server also goes down, or a EC2 health check failed, then also some notification should be set up.
If there is unusually high rate of HTTP 500s or 400s, alert send to dev team
For two we need to start using API Gateway so that these metrics star coming to cloudwatch. So blocked on Setup API Gateway #64
Logs and metrics should be stored.
Currently the logs are in syslog. Can we sent it to cloudwatch?
Also if the two services restart more than 3 times in half an hour, can we get an alert?
The text was updated successfully, but these errors were encountered: