Enterprise Distributed Application Service (EDAS) Agent sends heartbeat data from each instance to the EDAS console at regular intervals. The EDAS console uses this heartbeat to determine whether an instance is running. If EDAS Agent stops sending heartbeat data, the EDAS console marks the instance status as unknown.
The most common cause is that EDAS Agent has stopped working on the instance.
Diagnose the issue
To identify and fix the root cause, check the following items on the affected instance in order:
| Step | What to check | How to check | Action if the check fails |
|---|---|---|---|
| 1 | EDAS Agent process is running | Log in to the instance and check whether the EDAS Agent process is active. | Restart EDAS Agent. |
| 2 | EDAS Agent logs contain no errors | Review the EDAS Agent logs for errors or exceptions that caused the agent to stop. | Fix the reported error and restart EDAS Agent. |
After the underlying issue is resolved and EDAS Agent resumes sending heartbeat data, the instance status in the EDAS console returns to normal.