Currently we only take the first IP address in the bind statement. RS should instead use a priority of:
sentinel-announce-ip (same for port!)- First IP in
bind statement
It shall use this to determine it's name. In the event there is no bind statement AND no announce-ip in the sentinel config AND no address passed to red skull directly we will still need to determine an IP:Port string.
Another option to consider is to store a structured comment in the config file to name the sentinel, or looking in /etc/hosts for hostname (while still using the connectivity info above).
Currently we only take the first IP address in the bind statement. RS should instead use a priority of:
sentinel-announce-ip(same for port!)bindstatementIt shall use this to determine it's name. In the event there is no bind statement AND no announce-ip in the sentinel config AND no address passed to red skull directly we will still need to determine an IP:Port string.
Another option to consider is to store a structured comment in the config file to name the sentinel, or looking in /etc/hosts for hostname (while still using the connectivity info above).