You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens fairly often when the CSV pulled from AICC is either incomplete (bad network traffic) or a mistake was made in data entry that impacts the graph's ability to be drawn. All that needs to be done to fix this is to restart the app servers in ElasticBeanstalk. If we create an EventBridge, we should be able to have an IAM role that's only job is to restart that EB instance's app servers when things go bad. This fixes the problem 99% of the time, and would prevent erroneous alerts from Xymon about the issue and get the service up and running again even during off hours.
XREF #57 <-- Won't need this if we have this in place
The text was updated successfully, but these errors were encountered:
This happens fairly often when the CSV pulled from AICC is either incomplete (bad network traffic) or a mistake was made in data entry that impacts the graph's ability to be drawn. All that needs to be done to fix this is to restart the app servers in ElasticBeanstalk. If we create an EventBridge, we should be able to have an IAM role that's only job is to restart that EB instance's app servers when things go bad. This fixes the problem 99% of the time, and would prevent erroneous alerts from Xymon about the issue and get the service up and running again even during off hours.
XREF #57 <-- Won't need this if we have this in place
The text was updated successfully, but these errors were encountered: