I have an web application that uses other WCF services during servicing user requests and when one of them is failing the APM is displaying the requests and transaction as healthy!
For example,a page that experiences a problem and returns:
HTTP/1.1 500 Internal Server Error
in APM it most of the time displays fine, and only in the details of requet you can find the exception dat : http://img707.imageshack.us/img707/1097/capturemrf.jpg
So if APM is detecting a problem inside tansaction, why it is not signaling it?
This also happened to me during evaluation of AppDynamics Pro version and is clearly showstopper before any recommendation for purchase AppDynamics-APM. Please advise!
Thanks!
Jakub
Hi Jakub,
We Apologizes for the delay in response. To clarify the behavior on Lite , In Lite we do show whether the capture bad request (slow/normal/stall) had error or not using error column , in reference to screenshot we suspect that the error column is re-arranged as we see only 5 columns in the screenshot provided earlier by you. Can you try to expand the scrollbar to confirm whether the "error" column is exists but no error(red) symbol shown
If you still see the problem please attach the screenshot with expanded columns for "captured bad request" screen(with 7 cols in screen) and attach agent logs to debug further
Also can you please attach the relevant screenshot for the behaviour you have observed while evaulating in Pro
(you can see in the attached screenshots that request is signalled as error in Pro and Lite
We need your assistence to confirm and debug further
Thanks,
Arun
I did not hide or rearrange any column. The error column nr 3 remained empty. In the screenshot there are visible 6 columns and only 7th - transaction - is not visible. I do not have access to logs from that time so (evaluating PRO) , and also I have reinstalled LITE to newer version. Fortunately for this we still exception (will be fixed in next week) so I can provide you next screenshot. In this vernew ios the exception is visible in snapshots view so its better now but the exception is not reflected in schduled snapshots lists (on the right) while I think it should.
Generally I think (please correct me...) that the status of transaction is defined by the timing/performance and not the errors, so untill I had failing fast transaction ( WCF exceptions , HTTP 500 returned ) it was green, and only showed up yellow/red satus when it has slowed down. I would propose to put more emphasis on not only timing but also errors as they affect users same way or more than slow transactions.
(1) On the main screen in transactions list (there is calls/min, time, health) I would add errors/min per transaction.
(2) Erros/min nice chart in time is not clickable, o drill down possible - it's kind of useless, I'd like to be able to click particular point and see list of faile transactions in this time range.
Thanks
J.
Hi Jakub,
Apologies for the delayed response. It’s been sometime you have posted this. So please let us know the version of Lite that you are using.
I have done an internal test to double check the behavior and I could noticed that transactions with errors are indicated as error transaction, please find the screenshot for reference.
With respect to your other question please find the response inline:
(1) On the main screen in transactions list (there is calls/min, time, health) I would add errors/min per transaction.
:-This feature is already availabale.Please check the screenshot.
(2) Erros/min nice chart in time is not clickable, o drill down possible - it's kind of useless, I'd like to be able to click particular point and see list of failed transactions in this time range.
:-We can consider this as additional feature for the ADLite and will try for the future release.
Regards,
Swapna.