Application metrics page

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 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 Application metrics page

    The Application Metrics Page within IT Service Management provides access to critical performance and usage data for applications. This information is essential for evaluating application efficiency, identifying bottlenecks, and optimizing performance to enhance user experience.

    Show full answer Show less

    Key Features

    • Response Time: Measures the time (in milliseconds) it takes for an application to respond to user requests. Fast response times lead to improved user satisfaction.
    • DNS Lookup: Time taken to resolve a domain name into an IP address, affecting users' ability to access applications.
    • Page Load Time: Duration for a web page to fully display and become interactive, influencing user engagement.
    • Failed Web Requests: Number of unsuccessful retrievals of web content, aiding in identifying potential performance issues.
    • CPU Usage: Percentage of processing power an application consumes, with high usage indicating potential performance degradation.
    • Memory Usage: Percentage of RAM consumed by an application, crucial for resource allocation and avoiding crashes.
    • I/O Read and Write: Monitoring these processes ensures data retrieval and storage do not become performance bottlenecks.
    • Number of Crashes: Tracks application crashes over the last two hours, helping identify trends and improve reliability.

    Key Outcomes

    By utilizing the Application Metrics Page, ServiceNow customers can make informed decisions to optimize application performance, enhance user satisfaction, and proactively resolve performance issues to ensure a seamless user experience.

    Access the performance and usage data pertaining to a particular application. This information is critical for evaluating efficiency of the application, identifying bottlenecks and areas for optimization, and making informed decisions to improve its performance.

    Table 1. User device — Application metrics
    Cards Description
    Response time

    (Only web/SaaS applications have this field)

    		 Time it takes for a specific application to respond to a user request in milliseconds.
    Note:
    A slow response time can result in frustrated users, decreased engagement, and lower productivity, while a fast response time can lead to improved user satisfaction and increased engagement. Therefore, it is essential to track response time as a key application metric and continuously monitor and optimize it to ensure optimal user experience.
    DNS lookup

    (Only web/SaaS applications have this field)
    Time (in milliseconds) it takes for a user's device to resolve a domain name into an IP address.
    Note:
    If DNS lookup determines that there is an error in the mapping of DNS entries on the user's system, the user will be unable to access the internet or the intended website.
    Page load time

    (Only web/SaaS applications have this field)

    		 Time taken for a web page to fully display its content and become interactive upon a user's request.
    Failed web requests

    (Only web/SaaS applications have this field)

    		 Instances where requested web content or resources could not be successfully retrieved or loaded by the server.
    Note:
    The failed web requests result provides insights into potential issues affecting web performance. It helps in identifying problems such as server errors, broken links, or network issues that could hinder user experience. Understanding the frequency, type, and reasons behind failed requests helps in troubleshooting, optimizing web infrastructure, and ensuring a smoother browsing experience for users.
    CPU usage

    (Only installed applications have this field)
    Amount of processing power consumed by an application in percentage.
    Note:
    High CPU usage can result in degraded application performance, slower response times, and decreased user satisfaction. Therefore, identify performance bottlenecks and take proactive steps to optimize application performance.
    Memory usage

    (Only installed applications have this field)
    Amount of memory or RAM (Random Access Memory) consumed by an application in percentage.
    Note:
    High memory usage can result in degraded application performance, slower response times, and potentially lead to crashes or system instability. Therefore, monitor memory usage to optimize resource allocation and capacity planning, ensuring that applications have sufficient resources to meet user demands.
    I/O read

    (Only installed applications have this field)

    		 Process of reading data from storage devices, such as hard drives or solid-state drives, within a computer system.
    Note:
    Excessive I/O read operations can lead to performance bottlenecks, increased latency, and result in slower system response times. Therefore, monitor I/O read activities to ensure that the data retrieval processes do not become a limiting factor for application performance.
    I/O write

    (Only installed applications have this field)

    		 Process of storing or writing data to storage devices, like hard drives or solid-state drives, within a computer system.
    Note:
    Excessive I/O write operations can also lead to performance bottlenecks, increased latency, and potentially result in slower system response times. Therefore, monitor I/O write activities to ensure that data storage processes do not hinder application performance.
    Number of crashes

    (Only installed applications have this field)

    		 Trend of the application's crashes on the device over the last 2 hours.
    Note:
    Analyzing this graph enables you to identify potential issues, pinpoint trends, and take proactive measures to enhance the application's reliability and user experience.

    To return to the application metrics main page, see Users — Application Metrics.