TCP server with remote TCP endpoints

I have up to 30 TCP servers that need a heartbeat + a TCP message when it occurs in RabbitMQ queue. Webservers sends a small message to a RabbitMQ queue that will be sendt to one of the remote servers. Requirements - settings window where i can register TCP server IP and port - a PID for every connection (?) - Reload button on the client when remote server IP or port is updated. - Listen to a RabbitMQ queue for the message that will be sent to the remote server - Send only one TCP message at time, send next message or heartbeat when ack is received at the given interval. - Adjustable heartbeat from 20sec to 2 minutes. - Log sent and received to a database - Log to Slack - Simple API to retrive log This will be an internal service, not public againt internet. TCP servers is also internal. It can be a console window in linux, webpage, or a Windows application.