Based on your description, I assume you are running on Elastic Cloud? And by Fleet node I assume you shut down the APM & Fleet node in the Cloud UI? That would have been my first "go to" fix to get it resolved.
Can you check the content of the "hosted elastic agent policy"? I've seen a case before where something happened during migration and it did not contain a specific id that is needed for the hosted fleet-server to pick it up. Could you share the content of this policy here (without credentials of course)?
That is missing the fleet-server input. Which means the Fleet Server integration did not get installed into the Elastic Agent on Cloud policy as it should on first start up.
Thanks @blaker. We noticed that yesterday as well. We ended up manually installing the Fleet server integration and then had to terminate and re-enable APM&Fleet and it did end up connecting.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.