Hi, This is Ryotaro
In the transaction flow dashboard, please tell me the conditions under which the "transaction status" display around the tier turns red.
Because, even though there is an error count(DB exception), the session data display the "transaction status" still green.※picture1
(When drilling down to the target purepath, db's transaction status will also be displayed in red)
Why I couldn't see the transaction error on DB by transaction flow dashboard?
well, when I check your picture2 screenshot, the DB status actually is red? Check the transaction status (top right of the circle) of the database tier -> it is red. I think you are wondering, why on the most left side (the webserver) the transaction is still marked as green. The answer to that is that the overall response (given by the webserver) was obviously as a response code, which does not indicate a failure (e.g. Response code 200 - OK). Thus, the DB expection is present (and marked as said before), however it does not have that impact, that the whole transaction is failed (as the response code is ok).
You can check the response code in the respective PurePath by doing "right-click - details" on the most upper part of the call tree.
Generally, keep in mind, on the transaction flow: the upper right part (transaction) is flagged red, only then the respective tier is "seeing" the error (if the impact of an underlying error is throwed upwards).
Hope this makes sense.
Thank you for your answer, Dennis.
However, I don't wondering about "why on the most left side (the webserver) the transaction is still marked as green?". I'm wondering "Why displays the transaction of DB is still marked as green on Picture1(Picture 2 transactions are included) which has a DB exception error in the period?".
ah alright. How many transactions have been performed in that period? Because, what I dont see unfortunately, is if the transaction flow has analyzed ALL the transactions in the respective timeframe. If you have much more than 50000 transactions, the transaction flow will only analyze approximately up to 50000 to show data already. You can make a full analysis by clicking "full analysis" on the top. Might be that the ones which where failing, where not analyzed as part of your screenshot in picture1.
I can only confirm that it should be the way as you are expecting it (that it should be red on the first screenshot as well). If it is not, I think, some data is accidentially filtered out.
I think in this case a support ticket will be your best bet. I agree with Dennis that in this situation the DB transaction section should turn red. Maybe support will help us to find something that we missed.