Hey Elastic Team, Good Day, I'm done the configurations to autodiscovery of Heartbeat, and also it discovers the port, but the some of the up status ports in realtime in docker showing down from the beginning in the Heartbeat, Can you please help me figure out what could be issue, Attaching Screenshot FYI.
Anybody here?
Hi @itssenthil,
I can see the error message from your screenshot:
dial TCP 172.18.0.15:6650: connect: connection refused
Could you check if your heartbeat container has network access to the target service?
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.