,This appears to be quite normal to my knowledge. For reference, my test M10 cluster with 0 external connections is seeing around 45-70 connections (as per the last hour of the connections metric). With regards to the 100-125kb out, can you verify if thats the bytes out metric as opposed to the max bytes outs metric? I assume you have no activity on the cluster at all including any applications connecting, but correct me if I am wrong here as I believe the context of this question is more so in regards to resource utilisation for a cluster when there is no “activity” coming from external sources (applications, etc).
The majority, if not all, of those connections you’ve mentioned are most likely due to connections between nodes and other atlas agents. More details here.
It’s the number of concurrent (or active) connections at that period of time. So with your example, the 700 concurrent connections should be fine. However, in saying so, i’d go over the Review Available Metrics and Connection Pooling Overview documentation for more info.
Are you expecting 1500 concurrent requests for production workload? I think it may be better to try test the anticipated production workload against the server to see how it performs and whether or not there are enough resources.
I would check this with the Atlas in-app chat support team just to confirm any details or examples.
Hope some of these details help.
Best Regards,
Jason