You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/10/20 19:07:00 UTC
[jira] [Work logged] (ARTEMIS-4064) Harden MetricsManager
[ https://issues.apache.org/jira/browse/ARTEMIS-4064?focusedWorklogId=818905&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-818905 ]
ASF GitHub Bot logged work on ARTEMIS-4064:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Oct/22 19:06
Start Date: 20/Oct/22 19:06
Worklog Time Spent: 10m
Work Description: jbertram opened a new pull request, #4264:
URL: https://github.com/apache/activemq-artemis/pull/4264
In order to improve trouble-shooting for the MetricsManager there should be additional logging and exceptions. In all, this commit contains the following changes:
- Additional logging
- Throw an exception when registering meters if meters already exist
- Rename a few variables & methods to more clearly identify what they are used for
- Upgrade Micrometer to 1.9.5
- Simplify/clarify a few blocks of code
- No longer pass the ManagementServiceImpl when registering the metrics, but instead pass the Object the meter is observing (e.g. broker, address, or queue)
Issue Time Tracking
-------------------
Worklog Id: (was: 818905)
Remaining Estimate: 0h
Time Spent: 10m
> Harden MetricsManager
> ---------------------
>
> Key: ARTEMIS-4064
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4064
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to improve trouble-shooting for the MetricsManager there should be additional logging and exceptions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)