ASM - Out of the box Integration, query about Status Trend metric

Products

• CA App Synthetic Monitor

Issue/Introduction

Questions about various ASM metrics and their results in ASM and O2 Ui

Resolution

Q. Is the Status Trend the same thing as a Result Code?

A. The Status Trend metric is the same value as Status Code but expressed as an integer instead of a string. It's also the same value as the result code in ASM dashboard. 
Q. What's the reference of Soup in these error messages?

 Error Code 6001 Soup Cancelled
 Error Code 6002 Soup cannot resolve hostname
 Error Code 6003 Soup cannot resole -proxy hostname 

A. 'Soup' is a reference to the Soup HTTP client used in the old webkitgtk-based FPM agent. This was replaced by Chromium-based FPM years ago. The error codes remain the same as before but apparently the docs were not updated.

Q. Why is Status Trend showing a value of 6000 ? If you look at my screenshots, the Result Code shows 0 value for the same time frame.

A. With Direct Ingestion enabled, the check is performed from multiple locations at the same time. The value of the monitor-level metric is 6000 because one of locations reported an error code 6000. To find out which location it was, look at the location-level metric of the same name. 

In ASM UI Log Viewer and in the Infrastructure Agent only one of the simultaneous checks is displayed. It may not necessarily be the one that that reported the error 6000.

More information as to why the error 6000 may not be visible.  It is not an issue, it is a limitation of the ASM UI.
For example, if you have a monitor with three regions selected, then on every check interval, three checks are performed, one for each location. Two locations return Status 0 (OK), one location returns Status 6000 (Error). Out of these three results, ASM Log viewer shows only a single one. In this case it shows the result with Status 0 (OK). 

But in DXO2, metrics for all three results are reported.
That is why the error is not visible in the ASM UI but is visible in DXO2.

In a future release, will add a new log viewer into DXO2 UI that will include all the extra results. That will resolve the limitation. We will also add documentation explaining the differences from ASM. But right now the Direct Ingestion is still at a preview stage - it's not feature-complete.

If the Direct Ingestion was disabled, the check in the example above would be performed only from one of the three locations, the reported result in ASM would also be OK, and the error result would be missed entirely.

The Infrastructure Agent-based integration also reports only the single result shown in ASM.

Q. Is there an alternate metric to Status Trend and Result Code?
A. Yes , Use User Probe Failed