ServerMetrics does not support multiple ports properly

[yzfeng2020]

Currently, ServerMetrics is not designed to be per-port, which can lead to metric conflicts in the following scenarios:

• A single server instance serving on multiple ports.
• Multiple server instances running in the same JVM, each listening on different ports.

Since metrics are aggregated globally without distinguishing ports, this could cause incorrect reporting and make it difficult to track performance or diagnose issues per port.

We could introduce port as a label in ServerMetrics to differentiate metrics per port. This change would allow more granular monitoring and prevent conflicts in multi-port or multi-instance environments.

[ikhoon]

We could introduce port as a label in ServerMetrics to differentiate metrics per port.

Good idea.

[minwoox]

@yzfeng2020 Do you want to fix this by yourself?

[yzfeng2020]

@minwoox hey I won't have capacity for the next two weeks or so, feel free to pick it up if you, or anyone else have time!

[minwoox]

@yzfeng2020 I will implement this so it can be included in the next release. 😉