Statistics
The Highest Post







Statistics
Count 94
Avg 21.00
Min 21
Max 21
Angualr Top questions

Details



Step 2 – Weekly instance performance If routine tasks are a problem, finding errors, warnings, large log files, and slow jobs will help you get those tasks running smoothly. KEY INSIGHTS • Make sure your scheduled jobs run as they should. • Find the repeated errors and warnings in your logs. • Find data users logged excessively and large log files. • Determine if slow- or long-running jobs are causing issues. Review your scheduled jobs By reviewing your scheduled job activity, you can help ensure your background activities, such as scheduled reports, discovery sensors, and other routine tasks, run smoothly. Check for anything that’s running for more than an hour (3,600,000 ms). 1. Navigate to System Logs > Transactions (Background). 2. Apply a filter with the following conditions (see Figure 3): Created > on > This week URL > starts with > JOB Response time > greater than > 3600000 Note: The response may take several minutes to return. If you don’t return any results for an hour, try the same steps again with a more stringent value such as a half-hour (1800000 ms). Of course, some scheduled jobs are going to take a long time because they have a lot of work to process. Due to how the transaction log tables are stored and rotated in the database, it is not possible to use the “group by” function in the list view. Because of this, you may find it easier to do your trend analysis by exporting the result set to Excel. 3. If you see a job that has been executed multiple times for a long duration, drill down into what the problem is. The most common culprits are glide record queries, which request information from large tables with un-indexed “where” clauses or sorts/groups. These are often found inside of scripted transform maps and sometimes inside of script includes or business rules
Related Topics