feature request: expose qdstat data through metrics endpoint

[Kampe]

would be nice to be able to get the qdstat data of the routers and grab it with prometheus etc.

[grs]

There are some metrics already exposed in prometheus format for the router (basically equivalent to those you get from qdstat -g).

Just to check you have seen it, there are also some metrics available in json format through a get to /DATA on the skupper-controller service (that will be renamed), which is used by the console.

I do agree we want to do more for prometheus. One of the issues is whether/how to expose per-address stats and whether to expose at the router level or at the skupper services level. Improvements in this area are certainly on the list of things we want to tackle.

[Kampe]

I did see on the console some metrics exposed, however since there's no label applied to the console service I can't have the promtheues-operators easily scrape the service without creating my own version of it and labelling it accordingly. Putting any label on the service would be useful for the servicemonitor implementation.

Also, gathering any metrics at the moment does require the console deployed as well, not requiring that would be useful I'd imagine!