[
https://issues.apache.org/jira/browse/ARTEMIS-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820923#comment-16820923
]
Gary Tully commented on ARTEMIS-2308:
-------------------------------------
my 2 cent;
I think it would be sufficient to have artemis use the platform mbean server,
and only have the RBAC guard on the jmx remote secured endpoint that is
manages. That would provide a simple entry point for the jmx agent.
w.r.t to config, I think folks familiar with Prometheus will be content with
configuring the Prometheus way, a file url to the agent; it exists and is well
documented via examples.
on the http endpoint, I like that it can be controlled by the broker.
- Is there some way to enhance the existing prometheus jmx-exporter such that
the http endpoint and jmx-collector can be disconnected and independently
discovered?
- this is not a must have, b/c the open port with default (prometheus) value
may be expected by tools.
to [~michael.andre.pearce] point, I agree there is value in some abstraction
over metrics as exposed by artemis management, these metrics would bypass JMX
altogether and could be very performant.
> Support exporting metrics to Prometheus
> ---------------------------------------
>
> Key: ARTEMIS-2308
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2308
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Affects Versions: 2.7.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
