1- What are the criteria for Object Failure?
Answer: The HTTP return code for the object determines whether the object has failedd. Any return code not 2XX and 3XX range is considered an object failure. For more information, see Error Codes.
2- Are objects the same as web page resources?
Answer: Yes. Examples are .png, .js, .txt objects/files in the page source.
3- Does the test differentiate between base vs the 3rd party objects?
Answer: The test does not differentiate the objects from the base host vs. the 3rd party hosts. The Browser Agent sends the request to the server. Whatever the server sends back or directs to it, the Agent follows that information.
See Third Party Services Dashboard for information about analyzing the impact of 3rd party objects.
You can filter third party hosts out of the test. Download the test script to the Recorder (even if you created the test in the Portal vs. using a Recorder script, there is a script that can be downloaded and edited), then add a filter action as the very first action for a step. For details, see Opening a Script and Filter Script Action in the Dynatrace Recorder documentation.
4- Which conditions can turn the status of object failure? E.g. timeout, no response, response time higher than a limit?
Answer: Regular HTTP failures, timeouts, no response, or no response within a certain time can all be considered as object failure.