URL patterns to be ignored from monitoring
By default, this test does not track requests to the following URL patterns: *.js,*.css,*.jpeg,*.jpg,*.png. If required, you can remove one/more patterns from this default list, so that such patterns are monitored, or can append more patterns to this list in order to exclude them from monitoring. For instance, to additionally ignore URLs that end with .gif and .bmp when monitoring, you need to alter the default specification as follows: *.js,*.css,*.jpeg,*.jpg,*.png,*.gif,*.bmp
The URL patterns configured here are not just used by the eG agent to filter out unimportant performance data during metrics collection; these patterns are also used by the RUM collector to determine which beacons should be accepted and which ones need to be discarded.
Typically, the very first time this test runs and polls the RUM collector for metrics, the eG agent executing this test searches the performance records stored in the collector for data that pertains to the URL patterns configured for exclusion. If such data is found, the agent then ignores that data during metrics collection. This means that during the very first test execution, URL filtering is performed only by the eG agent. During this time, the RUM collector downloads the URL patterns configured against this parameter from the eG agent. Armed with this information, the collector then scans all beacons that browsers send subsequently, and determines if there are any beacons for the excluded URL patterns. If such beacons are found, the collector discards them instantly. Filtering URLs at the collector-level significantly reduces the load on the collector and conserves storage space on the collector; it also minimizes the workload of the eG agent. By additionally filtering URLs at the agent-level, eG makes sure that even if beacons pertaining to excluded URL patterns find their way into the RUM collector, they are captured and siphoned out by the eG agent.