Open Bue-von-hon opened 2 months ago
Micrometer already provides bindings to Netty Metrics (ref: https://docs.micrometer.io/micrometer/reference/reference/netty.html)
I prefer that we either: 1) We close this issue and allow users to add metric bindings themselves. Adding the metric bindings is not difficult and the scope of applying this metric seems ambiguous 2) We add bindings for servers only by default. The name will probably be a combination of local address + ports.
Let me know what you think @line/dx
I didn't know that Netty metrics were supported by Micrometer finally.
I prefer automatically setting the metric for the default one (ByteBufAllocator.DEFAULT
) when the MoreMeterBinders
class is loaded.
@ikhoon @jrhee17 @trustin @minwoox I trust this implementation satisfies your requirements. If the goal was to consolidate PooledByteBufAllocatorMetrics with eventLoopMetrics or certificateMetrics that would involve substantial modifications. (However, I don't believe that was the intended direction 😅)
Motivation: Add metrics related to PooledByteBufAllocator that are already exposed by the netty.
Modifications:
Result: Enables the PooledByteBufAllocator metric. this close #2633.