Clarify usage of proxy_address in remote cluster settings

[leemthompo]

elastic/elasticsearch#123215 for docsv3

cc @geekpete

[github-actions]

🔍 Preview links for changed docs:

• deploy-manage/remote-clusters/remote-clusters-settings.md

🔔 The preview site may take up to 3 minutes to finish building. These links will become live once it completes.

[yetanothertw]

Thanks, Liam and Peter!

[eedugon]

Very sorry for being late to the party @leemthompo and @geekpete , but I'd like to share my thoughts here, as I think further clarification would be more than welcome (I still feel this a bit vague and I have used it a lot in the past).

• For the first setting (proxy_address) we have:

The address used for all remote connections. A single address value, either an IP address or a fully qualified domain name (FQDN).

The first part feels a bit vague (what is all remote connections?). IMO ideally we should describe with something like:

The address used to reach the remote cluster. A single address value, either an IP address or a fully qualified domain name (FQDN). The port can be provided also. This endpoint typically represents a load balancer or reverse proxy that forwards the traffic to the transport endpoint of the destination {{es}} nodes. For example my-remote-cluster.mydomain.com:9400

• For the second setting (proxy_socket_connections), we say:

The number of socket connections to open per remote cluster

That per is wrong, because the setting itself is for a specific remote cluster, and not for others. We should say:

The number of socket connections to open towards the remote cluster

Of course it's configured per remote cluster, but that's kind of obvious and not the meaning of the setting. The setting is for this remote cluster that is being configured.

WDYT? The current descriptions create the wrong feeling that they are for multiple remotes, while the settings are for a single remote cluster configuration that will be connected through a single destination address and multiple sockets / connections.

[leemthompo]

Sounds good @eedugon I'll let you follow up, apologies, I should have left this open for the rest of the Admin docs team to have a look

[eedugon]

@leemthompo : Don't worry at all! I just found this by chance... but it's an area that confuses a lot to customers and engineers, and I don't think we have explained it well and clear enough (not these two settings, the entire remote clusters stuff).

So, the more love we can give on these little changes the better :)