Instance scan check to identify slow jobs in transaction logs.

Author: selvarun-umass

ca8467c41b9abc10ce0f62c3b24bcbaa/README.md

@@ -1,18 +1,4 @@
-# Generated files
-This repository contains generated files and a checksum.
+ ### Instance scan check to identify slow jobs in transaction logs.
 
-If you find yourself unable to import your repository due to the presence of files edited outside an instance of ServiceNow, merge commits that mix files from different revisions, or other data that does not match the checksum, you may recover using either of the following techniques:
-* Remove the problem commits:
-  1. Clone your repository to a personal computer with the git command line tools installed and open a git command prompt in the repository root
-  2. Run `git log` and take note of the SHA1s of the problem commits
-  3. Build revert commits using `git revert SHA1` repeatedly, working backward in time, for each commit that introduced changes not generated by a ServiceNow instance
-  4. Run `git push`
-
-* Overwrite the problem code snapshot with a known good one:
-  1. Clone your repository to a personal computer with the git command line tools installed and open a git command prompt in the repository root,
-  2. Locate a known good code snapshot and record its SHA1. For this step, `git log` can be useful.
-  2. Run `git reset --hard SHA1` to a commit that was generated by a ServiceNow instance
-  3. Run `git reset HEAD{1}`
-  4. Run `git add -A`
-  5. Run `git commit`
-  6. Run `git push`
+### Purpose
+The Instance Scan Check is a table check scan that allows administrators to investigate transaction logs in ServiceNow to diagnose performance issues reported by users. This check specifically identifies transactions with a **Response Time** greater than **120 seconds**, helping to uncover performance bottlenecks, understand user behavior, and track down issues within a specific time frame.