[
https://issues.apache.org/jira/browse/ARTEMIS-4497?focusedWorklogId=891172&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-891172
]
ASF GitHub Bot logged work on ARTEMIS-4497:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Nov/23 00:02
Start Date: 18/Nov/23 00:02
Worklog Time Spent: 10m
Work Description: erwindon closed pull request #4668: ARTEMIS-4497 export
summary on cluster-topology as metrics
URL: https://github.com/apache/activemq-artemis/pull/4668
Issue Time Tracking
-------------------
Worklog Id: (was: 891172)
Time Spent: 20m (was: 10m)
> export summary on cluster-topology as metrics
> ---------------------------------------------
>
> Key: ARTEMIS-4497
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4497
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Clustering
> Affects Versions: 2.31.2
> Reporter: Erwin Dondorp
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The broker has functions to export metrics to a metrics-interface-provider
> (e.g. [https://github.com/rh-messaging/artemis-prometheus-metrics-plugin] for
> collection using REST).
> This is only a subset of what can be collected using the JMX interface. (and
> the JMX interface has real commands too).
> Information on the cluster-topology was not yet available in these metrics.
> Due to the numeric nature of the metrics, providing the full topology of the
> cluster (as JMX operation {{listNetworkTopology}} does) is not possible. But
> just providing the broker-count is already very valuable.
> the following 2 metrics can be exported:
> * artemis_cluster_lives_count
> * artemis_cluster_backups_count
> With this information available, administrators can be alerted about various
> issues in the cluster. Detailed analysis can be done using the JMX info
> and/or the Console.
> a PR has been added to add that information to the set of metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
