✧ New feature
Improve the user experience, health, and performance of your application by analyzing application logs in combination with session replay. Empower your development team with all the tools they need to speed up the debugging process and fix bugs, crashes, and UI freezes in record time.
Errors tracking just got easier.
- Monitor errors, crashes, performance, and other issues, all within one tool.
- Identify bugs that weren't caught during the development process and the information you need for debugging.
- Verify that your application is working correctly, by analyzing requests sent, calls initiated, etc.
- Analyze warnings triggered during the session, such as login failures, security verifications, invalid parameters, etc.
- Filter by log type or find a specific log within a session.
All the information and context you need to improve error analysis and reduce debugging time.
- Enrich the analysis of the app logs with the visualization of the sessions, analyze gestures, actions, transitions between screens, and many other details.
- Compare the information in the app logs with the device and network details that UXCam captures automatically.
- Use session labels to categorize sessions with different errors.
- Collaborate with the team using notes and tag other team members to analyze and fix the issue faster.
Understand the impact on the business and user experience and prioritize more easily.
- Find and solve the problems that affect the key processes of your application and prevent users from converting.
- Prioritize errors, bugs, and other issues based on impact on user experience and product usage.
- Identify affected users to analyze their behavior and how errors affect the experience.
- Observe the impact of the different technical problems of your application in the main KPIs
You will find all these types of logs in your Dashboard:
Error: as its name says, a brief description of the problem encountered
Warning: It won't stop the application from running properly, but it’s something you could want to pay attention to, especially if in production.
Info: starting/stopping services, messages in the queue, etc
Debug: information that would be helpful for troubleshooting issues (what information goes there depends on developers and what they want to capture)
Verbose: very detail level about the workflow, again, depending on what you want to capture in this tracing.
Fault: need to check with the team
Undefined: if there’s nothing to evaluate on that log
What do I need to do to start tracking logs?
1- Update your SDK version. App logs are supported on versions equal to or higher than:
- Android Native 3.4.0
- iOS Native 3.4.1
- Flutter 2.1.0
- React Native 5.40
- Xamarin 3.3.0
- Cordova 3.5.1
2- Enable app logs from your UXCam Dashboard.
Click on your app > app settings > enable app logs
❗️Please make sure to review the logs for any sensitive user information before enabling it.
✓ You’re all set, the app logs will begin to appear in the logs tab in each of the sessions.
Find the sessions you want to analyze. As usual, you can filter by a certain segment, or apply any of the filters to analyze a specific platform, device type, group of users, or sessions based on activity or behavior.
Select one of the sessions to see all the relevant details and play the video. To see the logs registered on that session, click on the Logs tab, you can either see all the logs with the specific timestamp, filter by type of log e.i. Warning, or find a specific log with the search option.
» Understand the impact on the business and user experience and prioritize more easily.
For instance, you can find and solve the problems that affect the key processes of your application and prevent users from converting.
Log important events related to the purchase process that will help you with debugging and identifying issues with one of the key processes for your app.
Let’s say you have a food delivery app, then you can send these logs:
- Processing delivery request
- App has location permission
- App is online
- Request successful
While analyzing the purchase funnel in UXCam, you can then analyze drop-offs on a certain step, and drill down more into those sessions by analyzing the app logs and identifying if any of the actions or requests were not executed correctly.
» All the information and context you need to improve error analysis and reduce debugging time
For example, you can enrich the analysis of the app logs with the visualization of the sessions and all the details that UXCam captures automatically. Analyze gestures, actions, transitions between screens, device properties, and network details.
The OS prints useful logs automatically that could be useful in different cases. E.g. in Android, when the executions on a certain main thread code are taking too long and causing the UI to lag, the OS will print a message ‘Skipped 55 frames! The application may be doing too much work on its main thread’
By analyzing these logs together with the session replay and user experience, you can gather more details about the issue and analyze what’s the impact on the user experience. This helps understand the general performance of the app, uncover problems with the user experience, and prioritize accordingly.
» Analyze login failures and identify suspicious behavior.
Use UXCam to analyze warnings triggered during the session, such as login failures, security verifications, invalid parameters, etc.
Log authentication events to analyze login issues and identify suspicious behavior or attack attempts. With authentication events, you can analyze the login method, number of attempts, and login failures. You can print additional data to understand the reasons for the failure.
Additionally, you can use app logs to identify suspicious activity in almost real-time. For instance, seeing a high number of failed attempts in short times could indicate forced attacks, and if those events are followed by a successful login, you can prioritize and investigate this with urgency.
Label the user to monitor the behavior and activity, gather all the details about the device, location, etc., and combine this with the information provided by the app logs to investigate this further and fix any vulnerabilities.
» Analyze the stack trace of handled exceptions to identify the impact on the user experience.
Log the exceptions that were caught in your app to help you with debugging and understand their impact on the user experience and app performance. Then, analyze the stack trace with the app logs to identify these exceptions and handle them more gracefully.
For instance, let's say you have third-party libraries added to your app. An error occurred because you’ve sent the incorrect inputs to those libraries, the app will print a stack trace pointing to the problem.
With app logs and session replay, you can analyze this exception, understand which interaction in your app caused it, what the impact was on your app and features, and handle them more gracefully.