Configuration options for Pyrra internal metrics

[hsolberg]

Hi! I noticed that Pyrra exports its own metrics, but they are available in the frontend and not on a dedicated port? There's a mention in main.go of a parameter called MetricsAddr, but that's for the backend part of Pyrra it seems? This can be observed in the demo instance as well. I couldn't find any documentation on this, we would love to map that to a different port for Prometheus scraping.

[metalmatze]

Hey, great observation! Pyrra follows Prometheus in that regard, that runs the /metrics on the same port too. Pyrra also doesn't do any authn/authz, similar to Prometheus.

Are there any specific reasons you need to run this on a different port?

[hsolberg]

I was just worried about potential issues with SSL validation, but it works just fine. Would be nice to have the option for a dedicated port either way for flexibility.