[ 
https://issues.apache.org/jira/browse/ARTEMIS-5434?focusedWorklogId=966667&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-966667
 ]

ASF GitHub Bot logged work on ARTEMIS-5434:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Apr/25 07:40
            Start Date: 18/Apr/25 07:40
    Worklog Time Spent: 10m 
      Work Description: ViliusS commented on PR #5639:
URL: 
https://github.com/apache/activemq-artemis/pull/5639#issuecomment-2814839166

   > Just to clarify...In your environment you have exceptions with the same 
class names as those in ActiveMQ Artemis?
   
   For ActiveMQ Artemis not really. I just was going through all our 
environments and application packages, implementing JSON logging for proper 
integration with Google Cloud Logging. During this process I noticed the same 
error grouping issue with other Java software, not related to Artemis, which 
uses more generic exception names and also doesn't provide FQCN in the 
exception. I have already fixed this in those packages.
   Not sure if this change could breaks anything, but I thought it is good idea 
to change it everywhere, including the broker itself which we monitor 
constantly in our environment.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 966667)
    Time Spent: 1h  (was: 50m)

> Use full exception name in exceptions
> -------------------------------------
>
>                 Key: ARTEMIS-5434
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5434
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Vilius Ĺ umskas
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> It would be great to have full package name in the exception header. 
> Currently Artemis exceptions only include the short name of the exception. On 
> logging systems where exceptions are caught and tracked if they are repeating 
> errors (like for example Google Error Reporting), this groups different 
> Artemis exceptions into single error group.
> See 
> [https://github.com/apache/logging-log4j2/pull/3586#discussion_r2044006120] 
> for more information and screenshots.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to