The "Type" will report one of five values which represent the reason the check was run by ASM.
For example, a check of type 0 is a normally scheduled check and of type 2 corresponds to a second opinion check when an error occurs.
Here are the valid values:
0 = A normal check.
1 = An extra check (triggered via API call or an advanced monitor test check, etc.)
2 = A second opinion check when an error occurs.
3 = A check that occurs while the monitor is in maintenance.
4 = A final check (triggered by an error not requiring second opinion check).
5 = A check reporting an internal error from your OPMS checkpoint. (Meaning the OPMS was not able to run the check.)
Here is a sample output from a raw data export (The Resolve, Connect, Processing, Total and Download size columns were omitted to simplify the output.):
Date Start End Monitor name Monitor type Repeat Error description Code Alerts Location Resolved IP Type
8/16/2016 4:28:18 4:29:18 Test DNS dns 1 Not matched 9501 0 it 220.127.116.11 4
8/16/2016 4:28:31 4:29:31 Test HTTPS https 1 Service Temporarily Unavailable 503 0 r3 18.104.22.168 0
8/16/2016 4:29:45 4:30:16 Test HTTPS https 1 OK 0 0 n4 22.214.171.124 2
In the first example, Test DNS, the monitor reports a "Not Matched" error. Since DNS monitors do not make second opinion checks, the error is considered final and type 4 is reported. In the second example, Test HTTPS, the monitor initially reports a HTTP 503 error for its normal schedule check.
A second opinion check of type 2 is then launched to validate this error, but further issues are found.