Instance performance in Next Experience

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Instance performance in Next Experience

    ServiceNow customers can monitor and analyze the performance of their Next Experience instance using theclient interaction table. This tool provides detailed metrics about UI loading times and server response times for any recently accessed Next Experience page, with data retention of up to seven days. It enables identification and investigation of performance issues such as slow UI load times and network delays.

    Show full answer Show less

    Key Features

    • Client Interaction Table: Accessible via All > System Logs > Client Interactions, this table logs performance data including interaction timestamps, UI response durations, network latency, and server processing times.
    • Performance Metrics:
      • Total UI Time: Measures the full time from user interaction initiation to UI idle state, encompassing rendering and network delays.
      • Content Download Time: Duration spent downloading resources from the server within the interaction.
      • Network Latency and Cache Metrics: Includes approximate network round-trip time and browser cache hit rates to help compare regional performance and caching efficiency.
      • Server Response Metrics: Tracks total response time, SQL operation time and count, business rule execution time and count, and active transaction processing time.
      • UX Routing Details: Provides information on the screen route used, including parameters and screen variants, to better understand how pages are loaded and rendered.
    • Interaction Types: Differentiates between full page loads, single-page navigation, and in-page interactions to pinpoint where delays may occur.
    • Interruption Tracking: Records any page load interruptions that can impact UI timing metrics, aiding in root cause analysis.

    Key Outcomes

    • Enables proactive monitoring of Next Experience instance performance, helping to maintain optimal user experience.
    • Facilitates troubleshooting of slow UI loads and backend delays by providing granular timing and transaction data.
    • Supports performance comparison across regions and environments using network latency and cache metrics.
    • Improves visibility into the user interaction lifecycle and page load processes, allowing for targeted performance enhancements.

    View the performance-based information, including the UI loading times, for any recently accessed Next Experience page by using the client interaction table.

    Key benefits

    • Monitor your instance performance and view this information for up to seven days.
    • Identify and investigate performance issues, such as slow UI load times.
    • View the server response times.

    The following table lists the performance data that you can view in the client interaction table. You can find this table by navigating to All > System Logs > Client Interactions.

    Table 1. Next Experience client interaction table
    Header items Description
    Created Date and time that the interaction was recorded.
    Total UI Time Total time, in milliseconds, from when a user initiates an interaction, such as loading or navigating, until the UI is idle. Includes rendering and network request time, and may be affected by user interruptions.
    Content Download Time Total time, in milliseconds, spent downloading resources from the server during the interaction.
    UXF Screen Route Route that is used to load the page for the given experience. For example, if the page is accessed from a list or form, Classic is displayed. For a workspace, the route defined in UI Builder is displayed.
    Referrer URL that initiated the interaction.
    Application Application associated with the accessed URL.
    Type Interaction that is being measured. Type options include:
    • PAGE_LOAD: A full page load.
    • NAVIGATION: Routing within a single page application.
    • IN-PAGE: Time taken for interactions within the page, captured for limited interaction types.
    Interruption Type of page load interruption and information about the type of interruption. If there was no interruption, the record displays none. The page load interruptions can impact the total UI time metric.
    Name Contextual label for in-page interactions.
    Data Additional contextual details for in-page interactions.

    UI timing metrics

    • total_ui_time: includes network request time and rendering time.
    • fci_time (First Component Interactable): time when the user first interacts with the UI.
    • ui_time_before_load and ui_time_after_load: time before and after the application shell finishes loading. These values are not always populated.

    Network and download metrics

    • network_latency: approximate network round-trip time using a cached static resource. Useful for comparing performance across regions.
    • content_download_time: total time spent downloading resources during the interaction.
    • client_cache_hit_rate: percentage of requests served from the browser cache.

    Server and transaction metrics

    • total_response_time: total response time across all related transactions.
    • total_sql_time and total_sql_count: total time and number of SQL operations.
    • total_business_rule_time and count: time and count of business rule execution.
    • total_txp_time: time spent actively processing transactions, excluding wait times.

    UX routing details

    • ux_screen_route: the route used to load the screen in Next Experience.
    • ux_screen_fields and ux_screen_params: required and optional parameters used to load the screen.

    Additional data

    • linked_txc_metrics: JSON payload containing detailed client-side transaction metrics.
    • page_variant_sys_id: identifies the specific screen variant displayed to the user.