Overview

The MetaRouter Event Debugger provides visibility into event processing within your pipelines. This tool enables users to trace events through the system and inspect critical components like input payloads, output payloads, outbound requests, and vendor responses. This information helps users verify their deployments and troubleshoot issues with the data they're sending to vendors.

Access & Permissions

Important:

This feature displays full event payloads, including data like PII. Only users with the Debug Data Access role can access the Event Debugger. Take appropriate care when granting access or sharing data from this view.
If you are an organization Admin and cannot find the Debug Data Access role nor can you locate the Event Debugger, please reach out to your Customer Success Manager to activate the feature.

Using the Event Debugger

1. Navigate to the Event Debugger

From the MetaRouter UI homepage, on the lefthand navigation panel, click the Event Monitoring tab.
If not already selected, click the Event Debugger tab.

2. Select a Cluster

Use the Cluster dropdown to choose the environment (e.g., Metarouter Prod) from which to view events.

3. Apply Event Filters

Use the Event Search Type dropdown to refine your search:

Event Name: Find all events with a specific name (e.g., page, identify, product_purchased, etc.)
Message ID: Look up a specific event using its unique messageId.

messageId is a unique identifier automatically assigned to each event processed by MetaRouter.

Use the other filter controls to narrow your results:

Integrations: Filter events by destination/vendor integration.
Pipelines: Filter by pipeline name.
Status:
- Delivered: Event successfully sent to the vendor.
- Error: Event failed to send or received an error response.
- Filtered: Event was dropped by configuration rules.

Use the X icon to remove filters. Click the Refresh button to update results after modifying filters.

4. View Event Details

Click the icons in the Actions column inspect the event. A right-hand panel will open with four tabs:

Input

Shows the full event payload as it entered MetaRouter.

Output

Displays the transformed version of the event after it has passed through the pipeline/integration mapping and transformation logic.

Note:Not all integrations provide output visibility. Some may omit this tab due to their build type.

Request

Displays the exact API request MetaRouter sent to the vendor.

Note: This view may be empty if batch sizes were too large or if the integration does not support direct request logging.

Response

Displays the vendor’s API response to the above request.

Note: Filtered events do not generate output, request, or response data.

Troubleshooting Tips

To force a locally triggered event to appear in the debugger, use:
```
analytics.tracing(true);
```
To find the event in the Event Debugger, copy its messageId and search for it using the Message ID search capability.
If you’re not seeing updated data, verify that:
- Filters are set correctly.
- You’ve clicked Refresh after changing filters.
- Your event is recent enough to appear in the sampling window.
If you do not have access to the Event Debugger, check with your Organization Admin(s) to:
- Ensure the feature is activated for your organization.
- Ensure you have the Debug Data Access role active for your MetaRouter user.

Limitations

Debugger data is sampled and not comprehensive.
Output/Request/Response visibility varies by integration and event status.
Request data may be truncated or unavailable when batch sizes exceed UI limits.

For further assistance, please contact your MetaRouter support representative.