[
https://issues.apache.org/jira/browse/ARTEMIS-4655?focusedWorklogId=908064&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-908064
]
ASF GitHub Bot logged work on ARTEMIS-4655:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Mar/24 12:55
Start Date: 04/Mar/24 12:55
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4830:
URL:
https://github.com/apache/activemq-artemis/pull/4830#issuecomment-1976523689
I ran the full test suite job on this and it failed at the new test. I
pulled and rebased your changes locally and tried the test in isolation, and it
also failed in the same way. Seems that something is needing tweaked.
Issue Time Tracking
-------------------
Worklog Id: (was: 908064)
Time Spent: 1h 10m (was: 1h)
> Report logging metrics
> ----------------------
>
> Key: ARTEMIS-4655
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4655
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> External systems (e.g. Prometheus & Grafana) can consume metrics to visualize
> and monitor the health and performance of the broker. These systems often
> support configurable alerts to inform administrators of problems (e.g. long
> GC pauses, message accumulation, etc.). It may be useful to configure alerts
> for {{ERROR}} or {{WARN}} events in the log which may go unnoticed otherwise.
> The
> [Log4j2Metrics.java|https://github.com/micrometer-metrics/micrometer/blob/main/micrometer-core/src/main/java/io/micrometer/core/instrument/binder/logging/Log4j2Metrics.java]
> provided by Micrometer will report metrics for each logging category so
> administrators can see when unexpected events occur.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
