[jira] [Commented] (ARTEMIS-4655) Report logging metrics

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823517#comment-17823517 ] 

ASF subversion and git services commented on ARTEMIS-4655:
----------------------------------------------------------

Commit 661a4e6fdc1d10b115c209a25e96e6b97e75e8e6 in activemq-artemis's branch refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=661a4e6fdc ]

ARTEMIS-4655 report logging metrics

It may be useful to configure alerts for ERROR or WARN events in the log
which may go unnoticed otherwise.


> 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: 1.5h
>  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)