Advanced Debugging

Advanced debugging in VWO Feature Experimentation (FE) allows developers and product teams to monitor, identify, and resolve SDK-related issues directly within the VWO dashboard.

Traditionally, SDK errors appeared only in internal application logs, making it difficult to isolate VWO-specific issues. With advanced debugging, SDK-generated error logs are collected centrally and displayed in an intuitive console. This provides visibility into integration health, indicates the number of users affected, and enables you to quickly identify the root cause.

For example, if a feature flag fails to activate due to an incorrect key or initialization issue, the advanced debugging console displays the corresponding error, its frequency, and affected unique users. You can immediately determine whether the issue occurred in staging or production and troubleshoot without scanning large log files.

How does advanced debugging differ from SDK debug logs?

Advanced debugging exclusively captures error logs generated by the VWO SDK inside the VWO app. It does not capture internal customer application errors, logs originating from your application's code, or other external logs.

Key Benefits

With advanced debugging, you can:

• View critical SDK-generated errors such as initialization failures, retry attempts, missing feature keys, or network issues in the VWO interface without accessing internal server logs.
• Understand whether an issue is isolated or widespread by comparing total events with unique users.
• Filter logs by error category, SDK, and environment in which they occurred.
• Drill down into a specific error to view raw event data and timestamp, and identify the users who are encountering the issue.

📘

Read more here