How to troubleshoot Transactions (Increase) - Instance Observer alertsSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } This article will assist in identifying and mitigating the potential influx in transaction that can occur due to various factors, such as system overload, network congestion, or inadequate resource allocation, and provide guidance on effective strategies to manage and resolve these issues. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All releases of Instance Observer. Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Different scenarios that could lead to an increase in transactions on the instance. High User Load: A significantly larger number of users accessing the instance simultaneously than the instance is sized to handle.Integration Traffic: External integrations, such as MID servers or REST APIs, overwhelming the instance with frequent requests.Long-Running Transactions: Scheduled jobs or transactions that take an excessive amount of time to complete, tying up system resources.' Symptoms: Slow response times.Instance appears to be inaccessible.Stats and threads pages are accessible, but the user interface is not. Resulotion: Identifying the transaction count increase in Instance Observer. Go to Instance Observer and Click on "Performance" tab. Under Performance tab click "Transactions/Response Times". Add the desired instance name and date range, click on get snapshot. If there are influx of transactions, the transaction count graph will show a spike just like below screenshot. 2. Alternate verification method: Login to the instance, type stats.do in filter navigator and hit enter. In a new tab type threads.do in the filter navigator and hit enter. Gather and save stats.do and threads.Do, for instance. Note: If you are unable to reach the stats.do page, a restart of the instance or individual node may be necessary. Contact the ServiceNow Technical Support team to determine if this is necessary to perform the action.Refreshing the stats.do page will give you an idea of influx of transactions over time. Observe the Semaphore Sets section on the stats.do page over a few refreshes. The instance may be experiencing a high concurrency of requests if:Available semaphores is at 0 (zero), or remains very close to that.Currently waiting on a semaphore remains at 1 (one) or above.Semaphore transaction times are low (sub 1 second), but the above conditions are still true.If semaphore transaction times are long, then this is not a concurrency issue and is likely a blocking or other performance issue. If the long-running semaphores are mostly for the same URL (for example, /incident.do), then there may be an issue related to that individual page, and further troubleshooting of that page is needed. If the long-running semaphores are for various kinds of URLs, then there may be a resource constraint causing degraded performance. For additional information, see Troubleshooting slow performance. 3. To resolve a concurrency issue: Suspend activity at the source of the traffic, if possible. If this is a Management, Instrumentation, and Discovery (MID) Server or external integration, the owner of the system will need to take action. Note: To help identify the source of the increased request traffic, contact the ServiceNow Technical Support team.If transaction volume is related to normal user traffic, an incident must be created and assigned to Technical Support.