Exclude Virtual Pages from Being Monitored

You can exclude virtual pages from being monitored based on the virtual pages' URLs. You define exclude filters to match URLs of virtual pages that you don't want to be monitored. You cannot, however, exclude virtual pages that you are manually reporting with the SPA2 JavaScript API.

Virtual Page Object

The vp object contains the exclude filter that specifies an array of patterns to match the URLs of virtual pages to exclude. By defining an exclude filter, you automatically enable SPA2 monitoring.

"spa": {
    "spa2": {
        "vp": {
            "exclude": {
                 "urls": [{"pattern": 'api'}, {"pattern": "resources"}]
            }
        }
 }

JS

Virtual Page Filter Example

To use the virtual page filter, you set the JavaScript Agent with the exclude filter before you inject the adrum.js script.

For example, in the code snippet below, the pattern would match and exclude all virtual pages with URLs that have the strings "contact", "api", or "api" followed by one or more characters.

<head>
    <script type='text/javascript' charset='UTF-8'>
        (function(config){
            config.spa = { 			    
                spa2: {
                    vp: {
                        exclude: {
                            "urls": [{"pattern": "contact"}, {"pattern": "api*"}]
                        }
                    }
                }
			};
        })(window["adrum-config"] || (window["adrum-config"] = {}));
    </script>
    <script src='//cdn.appdynamics.com/adrum/adrum-latest.js' type='text/javascript' charset='UTF-8'></script>
    ...
</head>

JS