The Advanced Debugging feature in Wingify Feature Experimentation allows developers and product managers to monitor, identify, and resolve SDK integration issues directly within the Wingify dashboard.
Previously, if an SDK threw an error, it was recorded only in your internal server logs, making it difficult to isolate Wingify-specific issues. With Advanced Debugging, these logs are captured and presented in a centralized console. This provides visibility into integration health, helps you understand the impact of errors on your user base, and accelerates the resolution process.
For example, if a developer integrates the Wingify SDK but a specific feature flag fails to trigger for a segment of users, the Advanced Debugging console will capture the specific error code. You can then see exactly how many unique users are affected and identify whether the issue is occurring in your Staging or Production environment, allowing you to fix the root cause without sifting through massive internal log files.
Key Benefits
- Centralized Error Logging: View critical errors, retry attempts, and network failures directly in the Wingify interface without accessing internal server logs.
- Impact Analysis: Distinguish between the total number of error events and the number of unique users affected to prioritize high-impact issues.
- Granular Filtering: Isolate issues by specific SDKs (such as JavaScript, Go, or Android) and environments (Staging or Production).
- Detailed Stack Traces: Drill down into individual errors to view raw event data and identify the specific users (UUIDs) encountering the issue.
Prerequisites
- An active Wingify Feature Experimentation plan.
- Admin or Developer access level is required to view the logs.
- Wingify SDK successfully installed and initialized in your application.
How to access and use the feature
The Advanced Debugging console is located within your Feature Experimentation project. Follow these steps to access and analyze your logs.
Access the Logs tab
- Log in to your Wingify account.
- Go to Feature Experimentation.
- Select the specific project you want to debug.
- Select the Logs tab from the top navigation bar.
Filter and analyze log data
Once on the Logs tab, you will see a table displaying recent log messages. You can filter this data to isolate specific issues.
- Select a Time Range: Use the date picker in the top right corner to select the timeframe you want to analyze (for example, Oct 30, 2025 - Nov 13, 2025).
-
Filter by Category: Select the Category dropdown to filter by:
- Error: Critical failures in the SDK operation.
- Retry: Attempts by the SDK to recover from a failure.
- Network: Connectivity issues between the SDK and Wingify servers.
- Filter by SDK: If you use multiple SDKs, select the SDK dropdown to view logs for a specific platform (for example, Go, JavaScript, or Mobile).
- Filter by Environment: Select the Environment dropdown to toggle between Prod (Production) and Staging.
- After selecting your filters, select Apply.
Tip: Use the Unique Users column to gauge the severity of an issue. A high Total Events count with a low Unique Users count indicates that a few users are triggering the error repeatedly, whereas a high Unique Users count suggests a widespread issue.
Drill down into specific errors
To investigate the root cause of an issue, you can view the detailed stack trace and affected users.
- In the Log Message column, select the specific error message you want to investigate (for example, "Feature not found for api getFlag").
- A detailed view opens, showing two tabs:
- Events View: Displays the raw log message, timestamp, and the User ID (UUID) for every occurrence of the error.
- Unique Users View: Displays a list of unique users who experienced this error, along with the timestamp of the last occurrence.
Recommended Best Practices
- Check logs after deployment: Always review the Logs tab immediately after deploying a new feature flag or SDK update to Staging to catch integration errors early.
- Monitor Unique Users: Prioritize fixing errors that affect a high number of Unique Users, as these impact a larger portion of your audience.
- Use Staging environments: Filter by the Staging environment when testing new implementations to keep your Production logs clean.
Troubleshooting
If you encounter issues while using the Advanced Debugging feature, refer to the table below.
| Issue | Possible Cause | Recommended Solution |
|---|---|---|
| No logs are visible | The SDK may not be initialized correctly, or no errors have occurred yet. | Verify that the Wingify SDK is correctly installed and initialized in your code. Trigger a known error (such as querying a non-existent flag) to test logging. |
| Logs appear delayed | There may be a slight latency in processing log events. | Wait a few minutes and refresh the page. If the delay persists, contact Wingify Support. |
| "Feature not found" errors | The feature key used in your code does not match the key in Wingify. | Ensure the feature flag key in your code matches exactly with the key defined in the Wingify dashboard. |
Note: If you continue to face issues, contact Wingify Support for additional assistance.
FAQs
-
Is this feature available for all Wingify SDKs?
Yes, the Advanced Debugging feature supports logging for all major Wingify SDKs, including server-side (Go, Node.js, Python, etc.) and client-side (JavaScript, Mobile) SDKs.
-
Can I export these logs?
Currently, logs are viewable directly within the Wingify dashboard. For specific export requirements, please contact Wingify Support.
-
Why do I see multiple log entries for the same user?
If a user's device or application triggers the same error multiple times (for example, on every page load), it will increment the Total Events count while the Unique Users count remains the same.
-
Does this feature affect the performance of my application?
No, the logging mechanism is designed to be asynchronous and non-blocking, ensuring there is no impact on your application's performance.