Welcome to the Apica Help Center!

Check out our community, FAQs, articles and more!

Need assistance from Apica Support? Create a Ticket

I just set up an ASM check and it is failing on certain URLs. How can I handle this?

Answered

Comments

1 comment

  • Avatar
    Caleb Miller

    ASM gives users a high level of control over how they choose to see/interpret URLs that are displayed in the scenario results. For this particular instance, you'll want to use a combination of URL/file type/MIME type blocking and Severity Mapping.

    1. URL Blocking

    The Block URL tool is available in the Check Settings:

    Blocking a URL disregards any calls made to the URL from the check's waterfall results.  The most common reason to Block a URL entirely is because the performance of that URL is outside the responsibility of the Performance Team. Examples: Ad Services, Facebook, Google services, 3rd party services in general.  The format for blocking is 'subdomain.domain.com' - the protocol (http:// or https:// for example) is not needed, but you can keep any path to a specific file. You can utilize wildcards as well. Here are a few blocks as examples:

    2. Block File Types / Block MIME Types

    These can also be used to block calls by file type or MIME type:

    3. Severity Mapping

    Severity Mapping allows the user to assign a specific result status (Information, Warning, Error, or Fail) to a check despite receiving non-expected URL response codes. For instance, you can use Severity Mapping to "ignore" a URL that returns, for instance, a 404 instead of a 200 IF you don't care about the 404 error:

    Common reasons to use Severity Mappings where Blocks aren't a solution include:

    > Known recurring errors from a specific service or transaction that don't need to be sending out Failure alerts

    > Some specific background error that needs investigation, but doesn't need to send out Failure alerts

    > Monitoring 3rd party URLs without sending Failure alerts

    > Marking certain URL failures as Warning or Error rather than Failure

     

    It is worth noting that Severity Mapping works from top to bottom. If two Severity Mapping patterns map, the top one will take priority, so it will be the only one that matters. Take this into consideration when troubleshooting Severity Mapping.

     

    Preserve Value: Enable this option to preserve the Reported Value for a check run with URL errors that are mapped to I, W, or E (and there is no selenium error). By default a check run with URL errors is shown as a failed check run and the Returned Value is not saved.

    0
    Comment actions Permalink

Please sign in to leave a comment.