> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data/using-the-transaction-test-view.md).

# Using the Transaction Test View

The Transaction test view in **Network & App Synthetics > Views** shows the results for a selected transaction test. Use this view to identify the affected round and agent, then correlate transaction timing, browser object loading, script markers, screenshots, and console output for the same run.

This article focuses on the Transaction test view. For the standard layout used by Network and App Synthetics views, see [ThousandEyes View Layouts](https://docs.thousandeyes.com/product-documentation/internet-and-wan-monitoring/viewing-data).

## Opening a Transaction Test View

1. Navigate to **Network & App Synthetics > Views**.
2. Use the test selector to select a transaction test.
3. If the selected test includes multiple view layers, open the **Transaction** view.
4. Select the time range that contains the result you want to investigate.
5. Select a round in the timeline.
6. The detailed tabs update to show data for the selected round.

## Selecting Rounds, Agents, and Overlays

The timeline shows transaction metrics, such as transaction time, completion, timeouts, assert errors, page errors, and other errors. Use the timeline to compare behavior over time before you inspect a specific run.

To focus the view:

* Select a point in the timeline to inspect a single round.
* Use the **Agent** selector, or select an agent from the **Map** or **Table** tab, to inspect the run from a specific Cloud Agent or Enterprise Agent.
* Use overlays to highlight agents or script markers on the timeline without changing the filtered data.

Keep the same round and agent selected as you move between tabs. This keeps the evidence in the **Map**, **Table**, **Waterfall**, **Console Logs**, and **Dependent Applications** tabs aligned to the same run.

## Map Tab

The **Map** tab shows the agent locations that ran the selected transaction test. Use the map to identify whether a failure or delay is isolated to one location, one region, or many agents.

Select an agent location on the map to focus the rest of the Transaction test view on that agent. After selecting an agent, use the other tabs to inspect the detailed transaction result for the same round.

## Table Tab

The **Table** tab summarizes transaction results by agent. Use it to compare completion, transaction time, and error signals across the agents that ran the selected round.

Select an agent in the table to focus the view on that agent. For details about how the **Table** tab reports the date for transaction test data, see [Transaction Test Table Tab View](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/getting-started/transaction-test-table-tab-view).

## Waterfall Tab

The **Waterfall** tab shows the browser object loading sequence for the selected transaction run. Use it to inspect page loads, request and response timing, failed or incomplete objects, and markers from the transaction script.

For detailed guidance on interpreting waterfall charts for transaction tests, see [Navigating Waterfall Charts for Page Load and Transaction Tests](https://docs.thousandeyes.com/product-documentation/browser-synthetics/navigating-waterfall-charts-for-page-load-and-transaction-tests).

## Console Logs Tab

The **Console Logs** tab is the primary log surface for the selected transaction run when console log collection is enabled. It is separate from the browser developer tools console and from the Recorder console used during local Recorder playback. Use console logs to troubleshoot browser runtime errors, JavaScript errors, application messages, and intentional script-authored messages that are relevant to the selected round and agent.

### Enabling Console Log Collection

1. In **Network & App Synthetics > Test Settings**, open the transaction test.
2. Go to **Configure Test > Transaction Performance and Browser Settings (Optional) > Browser Options**.
3. Turn on **Collect console logs**.
4. Select **Next** to continue to **Configure Script**.
5. If you need script-authored messages in **Console Logs**, add safe and intentional `console.log(...)` or `console.error(...)` statements to the transaction script.

   Use script-authored console messages to mark script progress or capture sanitized failure context. For example, inside an async transaction script function that already imports `driver` and `until`:

   ```javascript
   console.log("Loaded checkout page");

   try {
     await driver.wait(until.titleContains("Checkout"), 10000);
   } catch (error) {
     const readyState = await driver.executeScript("return document.readyState");
     console.error(`Checkout page did not load: ${error.message}`);
     console.log(`Document ready state: ${readyState}`);
     throw error;
   }
   ```

   These examples are patterns, not required boilerplate. If a required step fails, rethrow the caught error after logging it. This keeps the transaction from continuing and returning misleading results. Do not log credentials, tokens, session identifiers, personal data, or other sensitive values.
6. Select **Instant Test** to validate the current settings and script behavior before saving the test configuration.

   An instant test runs with the current configuration, including unsaved changes to **Collect console logs** and the transaction script. Review the instant test result to confirm the expected messages appear in **Console Logs**.
7. Select **Update** to save the configuration if console log collection and any script changes should apply to scheduled test runs.

{% hint style="warning" %}
High-volume console output can affect transaction test performance and the results you see. If you need extensive debug logs, use them in an instant test first. Before you save changes for scheduled runs, remove or reduce high-volume messages and keep only short messages that support troubleshooting.
{% endhint %}

For more information about instant tests, see [Working with Instant Tests](https://docs.thousandeyes.com/product-documentation/tests/working-with-instant-tests).

### Viewing Console Logs

Use the same round and agent context when you review console logs and related transaction evidence.

1. In **Network & App Synthetics > Views**, select the transaction test that includes the run you want to inspect.
2. Select the time range and round that contain the scheduled or instant test result.
3. If you are viewing an instant test result, use **Open In New Tab** to view the result in its own browser tab or **Back To Views** to return to Views.
4. Open the **Console Logs** tab.
5. Use the **Agent** selector to select the agent whose run logs you want to inspect.
6. Use **Search** to narrow the table by **Time** or **Content**.
7. Review **Severity**, **Time**, and **Content** for each row.
8. If the table includes more rows than the current page, use **Show** and **Page** to move through the results.
9. Select a row to open its details.

   A details panel opens for the selected row. The panel header shows the row severity and time. The body shows the full message under **Content**. The **Content** section uses a read-only editor that detects JSON, HTML, XML, or plaintext for display. If a long message is truncated in the table, open the row details to inspect the full content.

The **Console Logs** table includes these controls and fields:

| Control or field      | Behavior                                                                                                                                                                                                |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Agent**             | Selects the agent run whose logs appear in the table. Keep the same agent selected when you compare **Console Logs** with **Map**, **Table**, **Waterfall**, and screenshots.                           |
| **Search**            | Filters the table by **Time** and **Content**. **Severity** is visible in the table, but the search filter does not search severity values.                                                             |
| **Severity**          | Shows the console log level for the row, such as **ERROR**, **WARN**, **INFO**, **DEBUG**, or **LOG**. Rows for system-generated messages, such as truncation notices, appear without a severity badge. |
| **Time**              | Shows when the log entry was recorded for the selected run.                                                                                                                                             |
| **Content**           | Shows the log message. Long messages are shortened in the table; select the row to inspect the full content.                                                                                            |
| **Show** and **Page** | Move through console log rows when the selected run has more rows than the current table page.                                                                                                          |
| Row details           | Opens when you select a row. The panel shows severity and time context, then the full message in the **Content** section.                                                                               |

The **Console Logs** tab shows a message when the selected agent, time range, or search returns no log rows. Use the message to choose the next troubleshooting step.

| Message                                                                                                         | Resolution                                                                                                                                                                                                           |
| --------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| "No console logs. Please try another agent or time range."                                                      | Select another value in **Agent**, choose another time range or round, and check **Console Logs** again. If logs still do not appear, include the selected agent, round, and time range in the ticket or escalation. |
| "Console Logs is not enabled for this test. Enable Collect Console Logs in Test Settings to view console logs." | Enable **Collect console logs** in test settings, then run **Instant Test** or wait for the next scheduled run. If you do not have access to change the test, send this message and the test name to the test owner. |
| "No console logs. Please ensure Collect Console Logs is enabled, then try another agent or time range."         | Confirm that **Collect console logs** is enabled. Then try another **Agent** selection or time range. If the setting is enabled and no logs appear, record that console-log data is unavailable for that run.        |
| "No console logs match your search."                                                                            | Clear **Search**, or use a shorter term from **Time** or **Content**. If the table still has no rows after you clear **Search**, troubleshoot it as an empty state.                                                  |

After you select the relevant run and agent, compare **Console Logs** with the same run's other evidence:

* Use errors or warnings on the **Map** tab and per-agent results in the **Table** tab to determine whether the issue is isolated to one location or affects multiple agents.
* Compare log timestamps and messages with the **Transaction Time** chart, the **Waterfall** tab, script markers, and screenshots.
* Use the **Waterfall** tab to inspect object timing and network request behavior. Use screenshots to confirm the visual state of the page when the browser, application, or script messages were recorded.

For information about screenshots in transaction results, see [Screenshots in Transaction Test Views](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/getting-started/screenshots-in-transaction-test-views).

## Dependent Applications Tab

If your organization uses the AppDynamics integration with ThousandEyes test recommendations, the **Dependent Applications** tab can show applications tracked in AppDynamics. Use this tab as additional context when a transaction failure might correlate with application health or service dependencies outside the transaction test itself.

## Troubleshooting with the Transaction Test View

Use the Transaction test view as a single troubleshooting workflow:

1. Use the timeline to find the failed or slow round.
2. Use the **Map** and **Table** tabs to identify the affected agent or location.
3. Use the **Waterfall** tab to inspect page loads, request timing, failed objects, and markers.
4. Use the **Console Logs** tab to inspect browser, application, and script messages for the same run.
5. Use screenshots to compare the visual state of the application with waterfall and console-log evidence.
6. If available, use **Dependent Applications** to compare the transaction result with application health data from AppDynamics.

This workflow helps you decide whether to investigate the transaction script, the application, a dependent service, the browser object load sequence, or the network path used by the affected agent.