Elastic Beanstalk Switches Between Ok and Warning with no Cause

0

I have an Elastic Beanstalk environment which sends me a notification at random points - usually around 10 times a day - stating only:

"Environment health has transitioned from Ok to Warning."

This issue always lasts exactly 1 minute before it switches back to Ok again.

There is no further information I can see on the reason for this - normally other degradation messages I receive include an explanation of the cause of the status change. I have checked my platform logs and can also see no obvious issue that is occurring any time around the status changes.

It is a staging server so activity on the server is also minimal. The monitoring shows things like CPU utilization and Network Out to be all very reasonable. I've tried streaming environment and instance monitoring to CloudWatch but only get the same basic error message.

I'm at a complete loss how I can determine the cause of the continuing status issue. I've even tried to sit there logged in on the AWS console ready for when it happens to see if the 'Causes' button becomes active! But as the issue always lasts under a minute, I've never been able to catch it in this state in time.

Any tips or advice about how I can determine the cause would be greatly appreciated as I am at a dead-end, and quite confused why AWS doesn't include the reason it's transitioned status in the message.

Many thanks!

Edited by: P000001 on Apr 23, 2021 1:23 AM

P000001
asked 3 years ago430 views
1 Answer
0

Managed to finally catch the environment in the console when it was down. It was a momentary spike in CPU usage for just a second, but I hadn't seen it in monitoring as by default it shows average CPU usage.

P000001
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions