Expose Metrics Endpoint on Different Port

[vbrandl]

Is there a way to start a second server listening on another port, so a /metrics endpoint is not publicly exposed?

The example would make the endpoint publicly available.

[davidpdrsn]

Use tokio::spawn or join to run a second server.

[vbrandl]

Yeah that works. Thank you.

Should the examples warn that it is bad practice to publicly expose the metrics endpoint or maybe even show a solution for running the metrics endpoint on another port?

If so, I'd be open to create a PR.

[davidpdrsn]

Sure!

[vbrandl]

I created #1444