Ask the Community
Store execution logs
Capture logs for all virtual users to enable comprehensive debugging and validation of your load tests
By default, BrowserStack Load Testing stores logs only for failed virtual users (VUs) to optimize storage costs. However, you can enable comprehensive logging to capture logs for all VUs, whether they succeed or fail. This is particularly useful for:
- Validating custom log statements or assertions
- Debugging intermittent or flaky issues
- Monitoring successful test executions
- Conducting deep performance analysis
Enabling comprehensive logging captures logs for all virtual users and may increase storage usage. This feature is disabled by default to keep costs low. Enable it only when you need detailed logs for debugging or validation purposes.
Depending on your preferred method, select any one of the following to enable execution log storage:
Enable execution logs in UI Builder
To capture logs for all virtual users in your load test:
Navigate to the BrowserStack Load Testing dashboard.
Open your test configuration or create a new test.
In the test configuration settings, locate the Capture all logs section.
Toggle the Capture all logs option to ON.
- When OFF (default): Only logs from failed executions are stored.
- When ON: Logs from all virtual users (both successful and failed executions) are captured.
Save your test configuration.
Click Run Test to trigger your load tests.
View execution logs
After your test completes:
Navigate to the Logs tab in the test results.
When comprehensive logging is enabled, you’ll see the following enhancements:
- Logs grouped by regions: Logs are organized by the geographic zones where your test ran.
-
Filter options: You can filter logs by:
- VU ID: View logs for specific virtual users.
- Status: Filter to show only successful or failed executions.
- Session indicator: The tab description shows “Showing logs from all sessions” to indicate that comprehensive logging was enabled.
BrowserStack retains execution logs according to its standard log retention policy, which applies to all test artifacts. For more information, refer to the BrowserStack data retention policy.
Configure execution logs in YAML
To enable comprehensive execution logging via CLI, add the storeAllLogs configuration to your YAML file. This configuration is applicable to both BLU (Browser-like User) tests and Hybrid tests.
Configuration for BLU tests
For BLU tests, add the storeAllLogs flag at the top level of your configuration:
This feature is available only for BLU tests, not API-only tests. In hybrid tests, you can use this feature only in the BLU portion.
username: BROWSERSTACK_USERNAME
accessKey: BROWSERSTACK_ACCESSKEY
projectName: First project
testName: First Playwright Load Test
testType: Playwright
language: nodejs
files:
dependencies:
- ./package.json
testConfigs:
- ./playwright.config.js
vus: 5
duration: 10m
regions:
- loadzone: us-east-1
percent: 50
- loadzone: us-west-1
percent: 50
storeAllLogs: true #store logs for failed and successful VUs
Configuration parameters:
-
storeAllLogs: The default value isfalse, settrueto enable execution logging.
username: BROWSERSTACK_USERNAME
accessKey: BROWSERSTACK_ACCESSKEY
projectName: First project
testName: First Hybrid Load Test
tests:
- testType: Playwright
browserLoadPercent: 10
language: nodejs
files:
dependencies:
- ./package.json
testConfigs:
- path/to/playwright.config.js
storeAllLogs: true #store logs for failed and successful VUs
- testType: JMeter
apiLoadPercent: 90
files:
testScripts:
- path/to/jmx_file.jmx
Configuration parameters:
-
storeAllLogs: The default value isfalse, settrueto enable execution logging.
By default, storeAllLogs is set to false, so the system captures logs only from failed virtual user executions. Set this to true to enable comprehensive logging.
Run your test
After configuring your YAML file, run your load test using the BrowserStack CLI:
browserstack-load run --config browserstack-load.yml
View execution logs
After your test completes, you can view the logs in the BrowserStack Load Testing dashboard:
- Navigate to your test results in the BrowserStack Load Testing dashboard.
- Click the Logs tab.
- When
storeAllLogsis set totrue, you see logs from all virtual users, grouped by region and filterable by VU, ID and status.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!