Ideas for Apica Synthetic Monitoring

Got an idea? Share it here and we'll have a look at it.

Severity handling Error wildcard setting improvement

Tooltip for today's "Error wildcard" checkbox:

If option enabled then mapping with code pattern '*' only applies to URLs having bad HTTP status (0, 4*, 5*).
Otherwise '*' applies to any HTTP status.

The problem with this setting is that there are many other statuses an URL can get, which are not covered here. For instance any case where the webserver cannot give a resonse code, "URL_TIMEOUT" etc. 

It would be to prefer that the function of this checkbox is inverted, so that instead of saying what statuses are bad, you state which ones are good (2*, 3*), and make all the others bad. Then it would be possible to use severity mapping even if there is no status code.

  • Guest
  • May 20 2015
  • Jun 18, 2015

    Admin Response

    This is a good idea, we need to review it further to see what we need to to in order to implement it in the best possible way. After that we will plan it into a release. We will come back to you with a more detailed release plan.

  • Attach files
  • Guest commented
    June 29, 2015 11:26

    Please take care of this! A lot of customers need this functionality.

  • Stepan Aksenov commented
    January 28, 2016 15:03

    If a URL has not got any HTTP status code (due to timeout), its code is represented as 0 in the system. So specifying * in the mapping would actually cover such cases.

  • Gravatar
  • Gravatar
  • Gravatar