How can I determine the one causing the slow loading on the instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
Do you have any other ways to check for the cause of the slowness in your instance?
Currently one of the user reported that when they are trying to access the my approval in the portal, they experience slowness in the instance.
When I tried to check the transaction logs, I can see the there are some entries that has more than 10 seconds of response time. Unfortunately I cannot pinpoint the exact cause for it just looking at the transaction logs and system logs does not give much also.
I also tried checking the slow transaction logs table but there is also not enough data.
Are there other places to check?
P.S. It is reported in a production instance so we have limitations and as of now we can only examine the logs and such. We have no permission for debugging so your guidance for where to check in logs or what to look for will be very helpful.
P.S. The instance is in Yokohama Patch 10 1a if there is any connected issues for that version.
Regards,
Vaine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello @Rain Vaine ,
Yes , you can check a few OOB performance pages in ServiceNow to understand whether slowness is instance-wide or affecting only a specific user.
You can start with Stats (stats.do) under System Diagnostics, which shows real-time performance details like response time, active sessions. If the numbers look high, it usually indicates overall instance performance issues. You can also review Slow Transactions and the Transaction Log (syslog_transaction) to identify long-running requests or scripts.
Please refer this thread :
If this helps you then mark it as helpful and accept as solution.
Regards,
Aditya,
Technical Consultant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello @Rain Vaine ,
When debugging is restricted, the key is correlation: align user reports with transaction IDs, then trace those across multiple log sources. Even without deep debugging, this triangulation often reveals whether the root cause is infrastructure, database, or custom logic.
I had also refer to the articles, it emphasizes correlating slow transactions with node-specific logs and using either the Debug Module or log file analysis to pinpoint whether the delay is caused by ACLs, scripts, database queries, or client-side rendering.
If my response helped mark as helpful and accept the solution.
