View (Page)¶

You can view the user's access environment, trace back the user's operation path, break down the response time of user operations, and understand the performance metrics of the series of backend application call chains triggered by user operations.

In the View Explorer, you can:

• Track user access data for each page, including load time, dwell time, and more;
• Combine data such as resource requests, resource errors, and logs associated with each page to comprehensively analyze the performance of the business application accessed by users, helping to quickly discover and optimize application code issues.

Explorer List¶

In the View Explorer, you can quickly view the page URL, page load type, page load time, user dwell time, and more for each user access.

Details Page¶

Click a data record in the list to open its details page, where you can view the page performance details of the user access, including Attributes, Origin, Performance, Trace Details, Error Details, and Related Logs.

Origin¶

In Origin, you can view the Session details of the current View, and filter/copy the current Session ID.

Performance¶

The Performance page helps you view the front-end page performance when a user accesses a specified application, including page load time, content paint time, interaction time, and input delay. Taking the following figure as an example, the LCP (Largest Contentful Paint) metric reached 8.4 seconds, while the recommended time is within 2.5 seconds, indicating that the page loads slowly and requires optimization.

For events on the current page, you can choose to display the most recent 50, 100, or 200 records, or all entries:

Obsy Copilot Error Analysis¶

Guance provides one-click error data analysis. It uses large language models to automatically extract key information from data and, combined with online search engines and operational knowledge bases, quickly analyzes possible failure causes and provides initial solutions.

1. Click a single data record to expand the details page;
2. Click "Error Analysis" in the upper right corner;
3. Start the anomaly analysis.

When analyzing App pages, Obsy Copilot can also combine page load, error, and resource request data to help identify suspected blank-screen issues, and provide related clues and troubleshooting suggestions in the results. You can directly ask, "Check whether the current page has a suspected blank-screen issue." Suspected prompts must be further confirmed against actual access conditions.

For more usage instructions, refer to Discovering Suspected Blank-Screen Issues in App.

Extended Fields¶

Attributes are the properties and characteristics of data objects, defining the value of each attribute.

In the search bar, enter a field name or value to quickly search and locate it;

After enabling field aliases, you can view the aliases after the field names; select as needed;

On the trace details page, you can view the related field attributes of the current trace in Extended Fields:

Related Fetch/XHR¶

When switching to Fetch/XHR, you can view every network request sent to the backend application during the user access, including the time of occurrence, the request's trace, and its duration.

If a network request has a corresponding trace_id, a small prompt icon appears before the request. Click it to jump to the details page of the corresponding trace.

Click a data row to choose to view the trace or resource related to that record:

Related Errors¶

When switching to Errors, you can view the error data information, error type, and error occurrence time for this user access.

Click an error message to jump to the details page of the corresponding error.

For more error details, refer to Error Explorer.

Related Logs¶

Through the Logs section at the bottom of the details page, you can view logs from the last 1 hour based on the current user access, along with the log count, and perform keyword search, multi-tag filtering, and time sorting on these related logs.

When related logs are opened, the system matches the log index mapping based on fields such as app_id, source, and service in the current detail data, and automatically selects the corresponding log index. The log count and the log list use the same index matching result.

• If you need more detailed log information: click the log content to jump to the corresponding log details page, or click Jump to go to Logs and view all logs related to this host;
• If you need to view more log fields or more complete log content: use the Display Columns of the related log explorer to customize Maximum Display Lines and Display Columns.

Note: For a smoother user query experience, Guance saves the user's browsing settings in Logs (including "Maximum Display Lines" and "Display Columns") instantly by default, so that Related Logs remain consistent with Logs. However, custom adjustments made in Related Logs are not saved after leaving the page.

Bound Views¶

Guance supports binding or deleting built-in views (user views) on the details page. Click Bind Built-in View to add a new view to the current details page.

For more details, refer to the document Binding Built-in Views.