Sentinet assigns a transaction status for each monitored message exchange. These statuses are color-coded by the Sentinet Administrative Console and explained bellow.
Success -- Successful message exchange.
Fault -- SOAP Faults or REST Application Faults intercepted or generated by the virtual services.
Error -- any message exchanges not identified as successful and not identified as SOAP Faults or REST Application Faults (for example communication errors are not Faults).
Inconclusive -- message exchange status cannot be determined at this time (but may be available later).
Sentinet differentiates SOAP Faults or REST Application Faults generated by the physical services or by the virtual services with all other errors and exceptions (for example with communication exceptions).
- Quite often SOAP Faults generated by business SOAP services or REST API application-level errors (REST “Faults”) do not have to be interpreted as erroneous cases and must be treated as “normal” operational conditions. Sentinet defines message transaction Fault status as the actual SOAP Fault or REST “Fault” received by the virtual service from the physical service. All other errors and exceptions are interpreted with the Error status.
- Most often, the resulting status of the transaction is determined by the status of its outbound side. In other words, the status of the message exchange with the backend service determines the complete status of the entire transaction including its inbound side (unless there were errors or exceptions before the business service was called, for example Access Denied exception generated by Sentinet).
- Inconclusive is a special status that may be temporarily recorded against a transaction. Its status cannot be determined at that time, because not all the required monitoring data was delivered to the Repository.