Web pages are made up of multiple objects. To properly construct pages, you must establish rules to differentiate types of objects:
is_promoted_documentexpression can be used to identify orphan Components.)
The object-type detection policy is a prioritized list of object-type detection rules. Each rule defines a set of objects and associates it with one of the four object types. Also see Configuring page detection.
By default, BMC Real End User Experience Monitoring Software Edition comes with object-type detection rules that define how the file types or HTTP statuses should be treated by the system.
Default object-type detection policies
http_status in (300, 301, 302, 303, 307)
url.extension in ("pdf","doc","xml")
url.extension in ("asp", "jsp", "do", "exe", "htm", "dll", "html", "shtml", "php", "ph3", "ph4", "php3", "php4", "php5", "phtml")
url.extension in ("js","css","gif","jpg","jpeg","png", "GIF", "swf")
mime_type = "text/html" or mime_type = "text/plain"
If a file does not match to any rule, it is considered as a container.
To view the object-type detection policies, go to a Real User Analyzer, point to Administration > Data flow settings, and click Object type detection.
The Default catch-all object-type detection policy covers the most typical use cases, but you might find situations in which you need to either alter its default rules or create a new policy. For example:
Because these exceptional issues are not handled by the default rules, you must either alter the existing rules or create a new object-type detection policy.
Object-type detection policy is a prioritized list of object-type detection rules that apply to an object when a certain condition is true.
To perform this procedure, you must have Operator-level access, or higher.
On the Administration page of a Real User Analyzer, click Object type detection.