Telemetry

From the Admin Console, you can view Telemetry to provide information for any errors that may be occuring across your deployed mods.

How to find telemetry

Go to the Admin Console and select Telemetry from the left side of the page.

On the Overview Page, you'll see a list of your deployments in a tbale, with their stauts, engagement, number of errors, and when the last error was seen.

This view is help for general monitoring and flagging any mods that have increased or recent errors.

Click the Error Feed tab to view a table of specific errors.

Each row provides helpful information about the scope of the errors, and details about where the error is happening.

Clicking the number in the Users column opens a modal with a list of users who have experienced the error.

Debugging specific errors

Use the Deployments and Mod/Step columns to determine where the error is happening. Scroll to the end of the row for more information about the specific error message, PixieBrix version, Platform (Browser Extension vs Web App), and a Request URL if relevant.

Use the Find feature in the data panel to search a brick name across a mod.

Once you've identified the brick it's happening in, it's helpful to activate the mod locally and follow General Mod Troubleshooting practices to debug the error.

Types of errors reported to telemetry

When a user encounters an error in the mod, it will be reported to mod telemetry.

Errors that are handled via Try/Catch will not be reported, unless you explicity use Raise Business Error brick.