Closed naude-r closed 1 year ago
@naude-r this seems more an issue for the Apache ActiveMQ Artemis MetricsManager.
@brusdev thank you, you are right. will log an issue with the artemis team.
ARTEMIS-4291 logged
@naude-r are you planning to create a PR to fix ARTEMIS-4291?
@brusdev yes, that is the plan.
PR 4487 submitted.
a new method, bind, was added to ActiveMQMetricsPlugin (default empty implementation). this was needed to make the order more explicit.
ARTEMIS-4291 merged for next release.
part of the above discussion resulted in additional metrics being added as well: ARTEMIS-4292 merged and available.
@naude-r great work!!!
@brusdev not getting jar and war file in repo
@gauravtayade11 this repository is supported by Red Hat, you can download the artifacts from the Red Hat public maven repository, i.e. https://maven.repository.redhat.com/ga/com/redhat/amq-broker/artemis-prometheus-metrics-plugin/2.0.0.redhat-00002/artemis-prometheus-metrics-plugin-2.0.0.redhat-00002.jar https://maven.repository.redhat.com/ga/com/redhat/amq-broker/artemis-prometheus-metrics-plugin-servlet/2.0.0.redhat-00002/artemis-prometheus-metrics-plugin-servlet-2.0.0.redhat-00002.war
currently the jvm metrics do not include the broker name. this is causing an issue when creating dashboards as the instance tag added by prometheus may not align with the broker name.
this might be as simple as:
meterRegistry.config().commonTags("broker", "XXXX");
not sure how to query the current server instance to get to the broker....