Useful or not, from you.
reactor-netty http server tcp.metric(true) should not expose remote_address

tcp.metrics(true) currently expose remote_address. This result OOM and cardinality issues.

reactor_netty_tcp_server_data_received_bytes_count{app="xxx",host="YYY",remote_address="127.0.0.1:45935",uri="tcp"} 2.0 reactor_netty_tcp_server_data_received_bytes_sum{app="xxx",host="YYY",remote_address="127.0.0.1:45935",uri="tcp"} 1292.0 reactor_netty_tcp_server_data_received_bytes_count{app="xxx",host="YYY",remote_address="127.0.0.1:45951",uri="tcp"} 2.0 reactor_netty_tcp_server_data_received_bytes_sum{app="xxx",host="YYY",remote_address="127.0.0.1:45951",uri="tcp"} 1292.0

Similar that #1075 Server metrics cardinality explosion

Normal springboot2 http_server metrics are enabled and tcp.metrics enabled using code below

@Configuration public class WebServerCustomizer {

@Bean
public WebServerFactoryCustomizer serverFactoryCustomizer() {
    return new NettyTimeoutCustomizer();
}

class NettyTimeoutCustomizer implements WebServerFactoryCustomizer<NettyReactiveWebServerFactory> {
    @Override
    public void customize(NettyReactiveWebServerFactory factory) {
        int five = 5000;
        factory.addServerCustomizers(server -> server.tcpConfiguration(tcp ->
                tcp.metrics(true).option(ChannelOption.CONNECT_TIMEOUT_MILLIS, five)
                        .doOnConnection(connection ->
                                connection
                                        .addHandlerLast(new WriteTimeoutHandler(2000, TimeUnit.MILLISECONDS))
                                        .addHandlerLast(new ReadTimeoutHandler(20000, TimeUnit.MILLISECONDS))
                        )));
    }
}

}

Reactor version(s) used: 0.9.10 JVM version (java -version): 8 OS and version (eg. uname -a): Windows 10

That's a useful answer
Without any help

@violetagg, Few reason:

  1. I did not managed to enable them, thanks for the tip how to enable them. This did not work. factory.addServerCustomizers(server -> server.metrics(true, s -> s).tcpConfiguration ....
  2. In the past we had cardinality issues in reactor_netty_http_client and thus we use end up using reactor_netty_tcp_client_*. tcp level expose less metrics and does not have uri dimension. response time and uri dimension result larger set of metrics and partially overlap with micrometer micrometer exposed http server metrics.
  3. reactor.netty.http.server.tls.handshake.time missing

I think you should remove the remote_adddress <port> from reactor_netty_tcp_server to eliminate the cardinality issues.