[jira] [Commented] (SIRONA-34) Failures counters should show the cause.

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

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

Romain Manni-Bucau commented on SIRONA-34:
------------------------------------------

ACtually current trunk only keep the exception type and the message and this is quite important to be able to aggregate exception. Sirona counters (path tracking is something else) are not here to debug (you can do it with logs). The issue otherwise is you can't aggregate consistently accross code and you get 1) too much exception compared to real issues, 2) not meaningful counter names (impossible to identify them in a container)

> Failures counters should show the cause.
> ----------------------------------------
>
>                 Key: SIRONA-34
>                 URL: https://issues.apache.org/jira/browse/SIRONA-34
>             Project: Sirona
>          Issue Type: Improvement
>            Reporter: Rahul Sharma
>            Priority: Minor
>
> When a failure counter is created attach the related stacktrace. This info can be shown in the view of the counter. This info is quite useful to drill down to the cause of the failure



--
This message was sent by Atlassian JIRA
(v6.2#6252)