The issue remains that in some cases the CA-SystemEDGE requires the agent to be started twice before it will start running.
The behavior of the APM agent coming up but the CA-SystemEDGE is not starting .
Inconsistent behavior of the CA-SystemEDGE running when using console_start or using a service to start the APMIACtrl.sh script regardless of which one of the two.
DX APM SaaS EM
APMIA with Host Monitor Extension
Current theory is that the start command is called too soon after stop, Sometimes maybe the SystemEdge taking a bit longer to stop, then the start command before it's completely stopped might be ignored.
Start command is executed after a while of Stop command and after checked the status of SystemEDGE