The contents of this article can be potentially performance impacting to your instance.
It is strongly advised to not run these reports during normal business / peak hours.
Should you observe performance degradation during the running of these reports then you should cancel your transaction.
Administrators may cancel the running report via Navpage > System Diagnostics > Active Transactions (All Nodes).
Every transaction in the platform will make an entry to this table, therefore querying this table in a long running report can potentially have significant impact.
Do not run these reports should you see impact.
Ensure these reports are not running during any performance debugging investigation
You may schedule the reports to run out of hours overnight and email you the results.
There are times when you wish to track changes in performance for certain types of requests, urls, over a period of time.
For example, after go lives, code changes, update sets, etc. This can be done by building out the following example reports.
Once built, you can add / modify them to;
- run weekly on a schedule and email a group of users overnight
- modify time periods to weekly, monthly, 6 monthly
- capture specific urls, eg: URL STARTS WITH /something.do (It is important to use STARTS WITH in this example, and NOT CONTAINS which can effect your instance performance)
Other options could be to modify the Aggregation field from 'Client Response Time' to 'Browser Time' or 'Client Script Time'
- for example if you're trying to track how long browsers take to render forms, or how much time Client Scripts take to run over your report time period.
> System Update Sets
You can also add a date range so that you can then run it week by week (schedule the report).
You can also add TYPE = form / list / report / (or none for all client transactions).
You could have a report for specific URL starts with /incident.do, /incident_list.do, /change.do, type = report, type = list etc.. so you can track different urls per time window and client transactions
Note: As this data is coming from the transaction log table, 'Client Response Time' is in ms - therefore 14,000 = 14 seconds.
Sample report definitions and output below;
Here are two samples (with output), of Type = FORMS last 7 days, and Type = FORMS, last 30 days
FORMS - Past 7 Days - Sample with Output
FORMS - Past 30 Days - Sample with Output