Explanation of errors
Sometime the information presented in an alert can be overwhelming, especially when you are in the middle of a severity 1 outage. In this article we walk through each of the errors, what they mean and common causes so that you can get the most out of PagePulse alerts.
Incorrect response code
When PagePulse makes a request it expects a specific HTTP Status code response. When the response received is different to what is expected you will receive this error.
Error as seen in an email alert
HTTP Status Codes
20X The request was successful.
30X The page you have requested has been moved to a different location. When these errors are encountered you will often see where the page has been moved to directly below the error in the alert as seen in the above example.
50X The was an error during the processing of your request.
For further reading on HTTP Status codes, check out this Wikipedia article.
Expected TeXt
This error occurs when we receive a response from the service but are unable to find the specified text on the page. You will find the text that PagePulse is expecting on the email alert as below.
Error as seen in email alert
Not expected text
This error is similar to 'Expected Text' but is opposite. This error occurs when we receive a response and find text on the page that we are not expecting. An example could be "Error occurred" or similar.
Response time
Response time alerts are issued when a particular step, page group or service takes longer than expected to execute. You are able to prescribe different levels of severity and this is shown in the alert together with what the limit and actual value was. When configuring response time alerts you are able to select from two separate algorithms for determining the response time:
Above the Line: Using this method, the response time must stay above the limit for the defined number of samples.
Rolling Average: Using this method, the response time is calculate by looking backwards over the defined number of samples.
Error as seen in email alert
Response time limits can be applied to a step, a page group or the entire script.
Max loops exceeded
This error occurs when there is a loop in the script and the specified maximum number of loops have been executed.
Error as seen in email alert
Page not found
You will receive this error when PagePulse does not receive a response before a time-out occurs or ther server responds with a 404 Http Status Code.
