Dynatrace integration for BrowserStack Load Testing

Learn how to send BrowserStack Load Testing metrics and events to Dynatrace so you can correlate load-test traffic with application and infrastructure performance.

Use this guide to connect BrowserStack Load Testing with Dynatrace so that you can correlate test activity with backend performance, infrastructure health, and user experience in a single place.

Prerequisites

Before you enable the Dynatrace integration, make ensure you have:

• Dynatrace environment: A Dynatrace SaaS or Managed environment that can receive metrics over the v2 metrics ingest API.
• Dynatrace platform token: A platform token created for a user or service account that has write access to metrics and events (for example, Storage: metrics: write and Storage: events: write). For details, see the Dynatrace platform token documentation.
• BrowserStack Load Testing account: Access to BrowserStack Load Testing with permission to configure integrations for your organization.
• Network access: Outbound access from BrowserStack infrastructure to your Dynatrace metrics ingest endpoint.

Integration overview

BrowserStack Load Testing streams metrics and events to your Dynatrace environment so you can analyze how your systems behave under load.

For an overview of all APM options, see Application Performance Monitoring integration.

Core capabilities:

• Metric streaming: BrowserStack aggregates performance data into short time buckets and pushes it to Dynatrace over HTTPS.
• Virtual user metrics: Track how many virtual users (VUs) are active, how long tests run, and how many requests they generate.
• Error and latency metrics: Monitor error rates and response-time percentiles to identify performance regressions.
• Browser metrics: For browser-based load tests, capture core web vitals such as LCP, FCP, CLS, and INP.
• Dimensions and tags: Each metric includes dimensions (for example, project name, test name, scenario, and region) so that you can slice and filter results inside Dynatrace.

Generate a Dynatrace platform token

Use a Dynatrace platform token so that BrowserStack can authenticate against the Dynatrace metrics ingest API.

Follow these steps in your Dynatrace environment:

After you generate the token, store it securely. You can reference it in your BrowserStack Load Testing configuration through an environment variable.

Supported metrics and dimensions

BrowserStack Load Testing sends the following metrics to Dynatrace.

Dimensions

Every metric sent to Dynatrace includes dimensions that help you filter and group data.

Use these dimensions to build focused charts and dashboards.

Lifecycle events

In addition to metrics, BrowserStack Load Testing can send lifecycle events to Dynatrace so you can align spikes or drops in performance with changes in test state.

Typical events include:

• Test initialized: Marks the setup phase and environment preparation.
• Test running: Marks the start of the main load window.
• Ramp up started / ramp down started: Indicates changes in active VUs.
• Test completed / passed / failed: Reports the final status and outcome of the test.
• Test timed out: Indicates that the test did not finish gracefully within the configured duration.

You can use these events as annotations on Dynatrace charts or in dashboards to understand what was happening during a particular time range.

Configure Dynatrace from the CLI

You configure Dynatrace integration in the browserstack-load.yml file. The following example shows a minimal configuration that enables Dynatrace and sends metrics to the v2 ingest endpoint.

This configuration lives under the top-level integrations block in browserstack-load.yml alongside any other APM tools you configure.

Best practices:

• Store the Dynatrace platform token (the apiToken value) in an environment variable (for example, DYNATRACE_API_TOKEN) instead of hard-coding it in the YAML file.
• Make sure that the Dynatrace endpoint URL and token match the region and account where you want to receive load-test data.

Next steps

After you save your changes to browserstack-load.yml, run your load test from the CLI or dashboard. When the test completes, open Dynatrace and search for the configured metric names and dimensions to validate that data is flowing correctly. Then build dashboards and alerts based on the metrics that matter most to your team.