Support for targeting non charm targets about prometheus-k8s-operator HOT 2 CLOSED

1. While supporting "external targets" is not the primary goal of the Prometheus operator some provision for external targets could certainly be made. What type of external scrape targets and configurations do you find to be common use cases ?
2. It is not clear why you need support for an "external target" (meaning not part of a charm) when you are trying to develop a charm that has a Prometheus metrics endpoint. If you have developed or are developing a HTTP Prometheus metrics end point why can you not just use a command line HTTP client such as wget or curl to check the "data exporting functionality" ? It is not clear to me what you mean by "Otherwise I have to write all of the code before I ever know if the data exporting works in the first place" ? What is this "all the code" that you refer to ? Is it the code of a your (scrape target) charm's event handler that handles the relation with the prometheus charm ? This code is mostly one function call add_endpoint(). If on the other hand it is the code that implements the /metrics endpoint, why can you not test this independently of your charm (such as using curl as mentioned) or any other way that is standard practice among developers of Prometheus metric endpoints ?

from prometheus-k8s-operator.

I discussed with @jlounder and it looks like this is best done through integrator charms which I had not considered.

from prometheus-k8s-operator.