Dockerfile mis-configure?
Opened this issue · 2 comments
Dockerfile exposes port 9119 but the prometheus server runs on port 9120. Is this what you intended?
Is this supposed to run on the sonarqube server? It's not built as an official "plug-in" so you have not provided sufficient documentation as to how it should run.
Hello, @Jaff!
This integration is a custom Prometheus exporter, which when requested, makes a call to the Sonarqube API that you define in the settings.
The Dockerfile facilitates the execution, being able to be executed from anywhere, not exactly on the Sonarqube server. But if you want to run on the same server as Sonarqube, that's also possible.
In short: the process needs to be running, so that it can make calls to the Sonarqube API, process/parse the information and expose the data as Prometheus metrics.
About the Dockerfile having port 9119 exposed, but the exporter running on port 9120, it was a mistake.
If you want to submit a Pull Request, correcting the configuration in the Dockerfile, feel free.