[
https://issues.apache.org/jira/browse/ARTEMIS-4675?focusedWorklogId=909931&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-909931
]
ASF GitHub Bot logged work on ARTEMIS-4675:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Mar/24 16:37
Start Date: 14/Mar/24 16:37
Worklog Time Spent: 10m
Work Description: alvinkwekel commented on PR #4844:
URL:
https://github.com/apache/activemq-artemis/pull/4844#issuecomment-1997871496
Hi @jbertram, thanks for your response.
I've added all cluster/replication related metrics that could to help with
debugging later. Looking at the activation sequence over time would give an
indication on restarts which could help to detect issues. Although I'm also not
too sure if it will fit in well with the other metrics.
Are there additional metrics you think that we should add for the
replication monitor use case? The "synchronizing" is not working as I expected.
What would be the way to get insight in the current state of synchronization?
Issue Time Tracking
-------------------
Worklog Id: (was: 909931)
Time Spent: 0.5h (was: 20m)
> Add replication status metrics
> ------------------------------
>
> Key: ARTEMIS-4675
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4675
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Clustering
> Affects Versions: 2.32.0
> Reporter: Alvin Kwekel
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Add metrics to be able to monitor the cluster replication status.
> Somewhat related to feature request ARTEMIS-4479.
> I've created a PR for this:
> https://github.com/apache/activemq-artemis/pull/4844
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
