Failed Column of "Web Services" built in dashlet
I've got a situation where one of our web service calls is failing with a soap fault (text of soap response attached below). However, the "failed" column of the dashlet is still at 0% for that service. I'm wondering what that column is measuring and how others are identifying soap faults in their applications.
Thanks,
Frank
Response Begin 06/26/2012 14:18:35 [Length=831] ----------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Header/>
<env:Body><env:Fault xmlns:ns5="http://schemas.xmlsoap.org/soap/envelope">
<faultcode>ns5:Server.PartnerFault</faultcode>
<faultstring>business exception</faultstring>
<faultactor>cx-fault-actor</faultactor>
<detail>
<ACORD xsi:schemaLocation="http://www.ACORD.org/standards/PC_Surety/ACORD1.10.0/xml/ bi-cmf-flat_V1_0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:htfd="urn:com.thehartford.bi.acord-extensions" xmlns="http://www.ACORD.org/standards/PC_Surety/ACORD1.10.0/xml/">
<InsuranceSvcRs><RqUID>5E4AD1A8-C037-B6D3-50D1-0DF4E5CC86BE</RqUID>
<htfd:AckRs>
<MsgStatus>
<MsgStatusCd>Error</MsgStatusCd>
</MsgStatus>
</htfd:AckRs>
</InsuranceSvcRs>
</ACORD>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
Response End----------------------------------------------------------------------------------------
Hi,
I think this might be a bug in the product then or maybe an enhancement is needed. This is a standard SOAP web service. The Web Services is returning a SOAP Fault. Since that's the standard mechanism used to identify an error in a Web Service call, I think the product should recognize it as an error. Or, at least have some way for me to configure it to recognize it as an error. Let me know your thoughts when you come back. It's not critical to our business at this time so I don't want to open a support ticket.
Thanks,
Frank
Hi Frank
You might be correct here. I looked at your session. Can you create a support ticket for this so that it gets officially forwarded to R&D?
Thanks
Got a little more feedback on this from engineering.
The Web Service Dashlet will only show an Error in case the Web Service call itself had an error. That means
a) If you have a call to a Web Service we look into that "send" method and verify if there was e.g: a 4xx or 5xx response code
b) If you have a call into a Web Service we check if there was any error within that web service implementation
In both cases we would mark the Web Service entry in the Web Service Dashlet as error.
We DO NOT mark the web services with an error in case the detected errors in the PurePath are not related to the Web Service call. That seems to be the case in your attached session. The errors you have are related to severe log messages that were captured in the purepath but not in the context of the web service call
hope this makes sense
Here is the session. If you look in the Web Services built in, the service call I'm referring to is "getQuoteProposal". If you drill into PurePaths from there, you'll see the ones that fail. They are all failing due to the Error Detection Rule I have set up called HIG_NBV_QPFailure_ERR. The condition in the rule is the Log Message contains "GetQuoteProposal service call failed".
Hey Frank,
I believe that since the error occurs in the PurePath outside of the Web Service call it marks the PurePath as failed, but not the Web Service (if the error occurred within the send() call's part of the PurePath it would mark both as failed). Is there a way for you to capture the error condition within the Web Service processing itself?
By the way, I'll be offline for a couple weeks starting tomorrow, so you might want to open a support ticket if this doesn't answer your question adequately.
thanks,
ted
Hi Frank,
That does look strange. For the 3 red PurePaths, what is the reason they are failing (i.e., what does the error tab in the PurePath dashlet list as the cause of the failure)? Can you maybe attach a stored session with the 6 PurePaths?
thanks,
ted
Hi Frank,
The Failure Rate percentage and the coloring of transactions red/yellow/green are driven by the "Error Detection" feature in dynaTrace. Basically, exceptions, logging messages, and http status codes can be configured to force a transaction into a failure state. You can review the error detection rules that are defined for your app by editing your System Profile and clicking on "Error Detection".
If your specific Web Service throws an exception or issues a logging message when it fails, you could use that to mark the transaction as failed.
thanks,
ted
Hi Ted,
I have an Error detection rule set up. And it is marking the purepaths red, but the "Failed %" of the Web Services built in dashlet is still 0%. I've attached a screen shot of the Web Services built in dashlet showing 6 service calls (0% Failed) and the 6 purepaths associated with those 6 service calls. You can see there are 3 Purepaths that are failed but still the Web Services Dashlet shows 0%. How do I get the Failed% on the Web Services Dashlet to reflect the failed transactions?
Thx. 
Community Member of the Month
December 2019
Announcing Dynatrace's Community Member of the Month for December 2019, Enrico F.! Click here to read more! Employee Member of the Month
December 2019
Announcing Dynatrace's Employee Member of the Month for December 2019, Silvia M.! Click here to read more! 