We have a java based application in which something is logged (using log4j or similar) at 'Error' severity level. Now, as per the default 'Error Detection' rules in Dynatrace (v 22.214.171.12471), it should just be "counted as error" and should not mark transaction or user action as failed.
However, in our case the purepaths are being marked with status as 'Error', and we are thinking that it might be a bug in Dynatrace. Could someone please clarify?
We have some custom validation logic which is failed due to this. Ideally, it should not have impacted the purepath's status by definition.
Thanks in advance,
Answer by Vaibhav M. ·
Thanks Adam. Doesn't it (marking purepath status as 'Error') constitute a "consequence"? As per the docs:
Each error detection rule defines the following consequences:
So, this means that purepath with 'error' status are probably not as bad as those having 'failed' status! It is just telling that something was logged at error/severe/fatal level which should be looked into, whereas the functionality might have worked fine. Performance (which we are interested in) might have been impacted though.
Answer by Adam G. ·
That is correct, Error markings are orange. Failed markings are red and thus count towards your failure rate. For an example, see the attached screenshot. The top purepath shows the default behaviour. My purepath has been marked as orange (Error) due to the out-of-the-box behaviour which denotes anything that starts with Error or FATAL or SEVERE to be marked as an error (Count as error).
In the bottom screenshot, I've created my own error rule but this time set the transaction to Count as error, mark transaction as failed. Thus my purepath goes red. Right click and show purepath details tells me why the purepath is marked as red (ie. which error rule it matched.)