In Laravel TeleScope’s Job Queries, some SQL statements are not documented

1. In Laravel TeleScope’s Job queries, some SQL statements are not recorded. Queries (22) is actually far more than 22. as shown in Figure 1

Figure 1

2. Check Laravel/Tescope in composer.json, its version is: v2.1.7 . as shown in Figure 2

Figure 2

Clear the table starting with Telescope_ and re-execute the Job. In Laravel Telescope’s queries, find all the sql under the job queries All exist, but some SQL is not associated with the job. It is estimated that there are more than 1000 SQL in the job, but in Laravel Telescope’s queries, there are only 641 sql, and it is still not fully displayed. as shown in Figure 3

Figure 3

4. Execute sql, select count(*) from `table`.`teleScope_entries` where `Type` =query, the result is 1375. Note that the SQL under the Job is fully documented, but not fully displayed. as shown in Figure 4

Figure 4

5. Enter an unrelated SQL, click View job, and it will jump to the latest job in the jobs, not the job it should be associated with. However, it is possible to confirm that this SQL is a Job that should have been associated with the value of the location. as shown in Figure 5

Figure 5

6. Decide to comment out some unimportant SQL execution in the job to reduce the number of SQL so that you can observe more important SQL.