{"id":4871,"date":"2024-08-07T07:03:36","date_gmt":"2024-08-07T07:03:36","guid":{"rendered":"https:\/\/www.aegissofttech.com\/insights\/?p=4871"},"modified":"2025-12-19T13:10:38","modified_gmt":"2025-12-19T13:10:38","slug":"servicenow-xmlstats-do-command","status":"publish","type":"post","link":"https:\/\/www.aegissofttech.com\/insights\/servicenow-xmlstats-do-command\/","title":{"rendered":"Troubleshooting in ServiceNow: Deep Dive into the xmlStats.do Command"},"content":{"rendered":"\n

Troubleshooting in ServiceNow: The xmlStats.do Command Tutorial<\/h2>\n\n\n\n

In ServiceNow, the `xmlStats.do` command is a powerful diagnostic tool used to monitor system performance. The command \u201chttps:\/\/instance.com\/xmlastats.do\u201d provides detailed XML output containing important statistics about the system’s health, including memory details, active sessions, node performance, and database activity. For organizations leveraging ServiceNow Managed Services<\/a><\/strong>, this tool plays a crucial role in proactively maintaining optimal performance and ensuring a smoothly managed environment.<\/p>\n\n\n\n

This information is crucial for administrators to identify system performance and ensure the instance runs smoothly. This command can be essential for effective system monitoring and troubleshooting in ServiceNow.<\/p>\n\n\n\n

Post San Diego\u00a0release, the System Diagnostics homepage is deprecated ,which provides system performance metrics. By default, new instances post San Diego version do not have a System Diagnostics homepage. \u00a0It was truly the best tool to understand the instance health and optimize the instance performance. However, the `xmlStats.do` command can be a valuable alternative.<\/p>\n\n\n\n

Overview of various components of xmlStats.do<\/strong> and how to interpret them<\/h2>\n\n\n\n

Node Details:<\/strong><\/h2>\n\n\n\n

This section gives clear picture of nodes available, and their status.<\/p>\n\n\n\n

In addition, it also gives if they are available for AHA readiness (Advanced High Availability Readiness)<\/p>\n\n\n\n

\"Node<\/figure>\n\n\n\n

Flow Details:<\/h2>\n\n\n\n

This section shows information about executed flows and details about the Flow Engine Event Handler. This helps to troubleshoot issues related to flow execution, such as flows that are not running or are stuck.<\/p>\n\n\n\n

\"Flow<\/figure>\n\n\n\n

Semaphore details:<\/strong><\/h2>\n\n\n\n

Semaphores define number of transactions that a node can execute. This can be analysed to understand node health with respect to transactions.<\/p>\n\n\n\n

\"Semaphore<\/figure>\n\n\n\n

Thread details:<\/strong><\/h2>\n\n\n\n

Threads are similar to semaphores. Worker threads are responsible for executing scheduled jobs.<\/p>\n\n\n\n

The Thread metrics can be analysed to understand the long-running scheduled jobs in the instance.<\/p>\n\n\n\n

\"Thread<\/figure>\n\n\n\n

Pending schedule jobs and update sets installed in last 24 hours:<\/strong><\/h2>\n\n\n\n

This section provides information about pending scheduled jobs and updates installed in the last 24 hours. It helps in troubleshooting long-running jobs and identifying recent updates that might be affecting system performance.<\/p>\n\n\n\n

\"Pending<\/figure>\n\n\n\n

Current logged-in<\/strong> user’s details<\/strong><\/h2>\n\n\n\n

This section shows the number of users currently logged in per node, as well as a role-wise user count. This helps administrators understand node performance concerning user transactions.<\/p>\n\n\n\n

\"Current<\/figure>\n\n\n\n
\"Current<\/figure>\n\n\n\n

Inbound and outbound email metrics:<\/strong><\/h2>\n\n\n\n

Inbound and outbound email processing is crucial in any instance. Particularly if the instance is a production instance, it is important that the instance processes inbound emails for various inbound actions and outbound emails for various communications.<\/p>\n\n\n\n

The metrics give processed count, time and related jobs. This helps to understand system performance in terms of sending and receiving emails<\/p>\n\n\n\n

\"Inbound<\/figure>\n\n\n\n

Plugin Details:<\/strong><\/h2>\n\n\n\n

This section lists all the plugins installed in the instance, their versions, and installation dates. This information helps quickly identify when specific plugins were installed in the instance.<\/p>\n\n\n\n

\"Plugin<\/figure>\n\n\n\n

In addition to the above metrics, other important information like instance data replication details, event details, mid servers in the instance details, URI response times, JVM details and memory details in the instance can be found from the xmlStats.do the command. This information provides a comprehensive view of the instance performance health.<\/p>\n\n\n\n

The \u201cInclude\u201d Argument:<\/strong><\/h2>\n\n\n\n

Use the xmlStats.do?include=<section> command to pull up specific section details. Instead of pulling up the whole XML output of the ServiceNow instance performance<\/a>, this argument can be used to specify a piece of information the admins need.<\/p>\n\n\n\n

For example, to only get thread details, use xmlStats.do?include=threads<\/strong>. This helps to get more understandable pieces of information from a complex XML output.<\/p>\n\n\n\n

Helpful docs:<\/strong><\/p>\n\n\n\n