-
Notifications
You must be signed in to change notification settings - Fork 7
InstanceDown
tei-k edited this page Jun 2, 2020
·
1 revision
This alert indicates that one or more instances is not reporting as being up. The alert will include which instance is being reported as down and the action needed may vary. This alert is not always critical to the overall environment but it could indicate a potential problem if not resolved.
[prodtest-f4vofpw][FIRING:2] InstanceDown critical
reaper.internal.scalar-labs.com:9100 - firing -
scalardl-blue-1.internal.scalar-labs.com:9100 - firing -
[prodtest-f4vofpw][RESOLVED] InstanceDown critical
reaper.internal.scalar-labs.com:9100 - resolved -
scalardl-blue-1.internal.scalar-labs.com:9100 - resolved -
- A good place to start is to check the log output for reported instance to see if it gives a reason why it went down.
- If the instance is not critical you can wait a few minutes to see if it recovers on its own. Most services will restart automatically.
- Check the cloud provider to see if there are any known issues in the deployed location.
- How to access the log server
- How to restart a down service