19.浏览器监视器高级设置

MON-SYN-220_Browser Monitor Advanced Setup
Advanced setup options allow you to fine tune the behavior of your synthetic browser monitors. During monitor creation, these are available as ‘Additional options.’ After creation, edit the browser monitor and go to Advanced setup.
For single-URL browser monitors, enable global login authentication to automate sign-in to password-protected pages. Dynatrace LoginSense technology allows a monitor to securely log into your application. Select ‘web form’ if your application uses an HTML-based login form. ‘HTTP authentication’ is used for browser-native dialog boxes, typically for basic, digest, NTLM, or Negotiate authentication methods. These use a name and password stored in the credentials vault. When you create new credentials, specify a name, the username and password, and then save them to the vault.
This centralized repository securely stores credentials in Advanced Encryption Standard– encrypted form. The encrypted credentials are visible only to the synthetic monitors that use them, not to users. The owner/creator of the credentials can choose to make them available to other users with credential vault access. Credentials can be overwritten when usernames or passwords need to be updated. The credentials vault may also store certificate files, tokens, and public certificates. For clickpaths, only basic HTTP authentication is available and can be found in the properties of the Navigate event.
Each browser monitor is created with the minimum set of headers required. To expand these, enable additional HTTP headers. Enter the headers and values. To apply these to specific requests only, define a request matching pattern.
To analyze the effects of specific requests, you can experiment by blocking them in the synthetic monitor instead of changing your application.
Use ‘Set cookies’ to simulate an application state. Ensuring each monitor execution is based on the same state will generate meaningful synthetic baselines. Enter the cookie name and value and specify the domain and path for which the cookie is set. The cookies are sent with monitor requests and are valid for the entire monitor execution. For a clickpath monitor, add a synthetic event. Set the type to cookie and enter information. This applies the cookie to this part of the clickpath.
Flip this switch to allow Chrome to bypass an enabled content security policy on monitored pages when the monitor executes. A CSP may prevent the browser from sending monitoring data to Dynatrace.
Flip this switch to capture performance data for pages in iframes or framesets. Resulting data will contain waterfall results for each frame.
Enable the custom JavaScript Agent settings to use different settings than those configured for real-user monitoring in the application. Customize the JavaScript framework support as you would for an application.
Content capture can be configured for the following:
Enable JavaScript error reporting.
Detect actions that trigger XHRs via setTimeout methods.
Extend action duration for XHRs triggered within cascading setTimeout methods.
Configure settings for ‘Visually complete’ and ‘Speed index’ calculations.
Add JavaScript agent properties specific to this synthetic monitor. These are custom properties defined as key-value pairs. These should be used carefully and for debugging purposes only.
These Advanced setup features expand your synthetic browser monitors beyond availability and performance, allowing you to simulate comprehensive user journeys under varying conditions without needing to change your applications.