Hi Clebert, Apologies for the belated reply,
I used the prometheus jmx-exporter <https://github.com/prometheus/jmx_exporter> as kind of a hack to adapt a pre-built binary to play better in k8s. I wouldn't leverage it for the upstream development. Personally (this is totally just-in-my-opinion land, feel free to ignore me) I'd leverage something like http://micrometer.io/ from pivotal, which is kind of a SLF4J but for metrics. It has output bindings for: AppOptics, Azure Monitor, Netflix Atlas, CloudWatch, Datadog, Dynatrace, Elastic, Ganglia, Graphite, Humio, Influx/Telegraf, *JMX*, KairosDB, New Relic, Prometheus, SignalFx, Google Stackdriver, StatsD, and Wavefront. That'd make artemis a much more compelling cloud player, not just k8s but also AWS, GCE, Azure, etc. It would require some decent level of work to change artemis->JMX to artemis->micrometer->JMX|others thow. Thanks El lun., 18 mar. 2019 a las 14:32, Clebert Suconic (< [email protected]>) escribió: > I was doing some quick tinkering with what Victor Romero did on his > docker image for artemis, > > and I tried to bring it into Artemis, > > I inteded to allow users to do with the create command: > > ./artemis create FOLDER --jmx-exporter > > > and that would be enough to enable Prometheus JMX exporter. > > > however, the way I did, by changing artemis.profile, made the agent to > also be used within other CLI commands such as exporter, print-data.. > etc... > > > So, I am wondering what is the best way to deal with this: > > > > I needed to only enable the exporter on the run command, however I > need the --javaagent to have it working. > > > Here is a prototype: > > https://github.com/clebertsuconic/activemq-artemis/tree/prometheus > > > I thought about tinkering with the shell script, looking for some > arguments in a way it would be enabled on run. > > > Any ideas? > > -- > Clebert Suconic >
