- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-26-2018 06:34 PM
Short of adding a counter to a couple dozen Business rules, is there any way to keep track of how many times a specific business rule has run in the last day, week, etc?
We are currently experiencing issues with our Incident space, and based on the Transaction logs, the business rules and more specifically the quantity of them is the offender. My assumption is there are a few outliers that could be a quick win to refactor to help our business partners who are feeling the pain of the poor performance.
Thanks in advance.
Solved! Go to Solution.
- Labels:
-
Performance Analytics
-
Reporting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2018 01:24 PM
Hey Stephen,
Does the issue you're seeing have to do with querying? If so, there is the Slow Queries table under System Diagnostics that groups queries together, and aggregates what the average execution time and measures how many times those queries have been executed.
For example:
This is aggregating all the times that the business rule "SAM License Counters" ran, and shows what query it's launching. In my sandbox instance, it has run around 1m times since September 2017, and has an average time of 20 minutes to complete.
That way, you can sort it not only by volume, but also by average time to complete / total time consumed, etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-27-2018 01:24 PM
Hey Stephen,
Does the issue you're seeing have to do with querying? If so, there is the Slow Queries table under System Diagnostics that groups queries together, and aggregates what the average execution time and measures how many times those queries have been executed.
For example:
This is aggregating all the times that the business rule "SAM License Counters" ran, and shows what query it's launching. In my sandbox instance, it has run around 1m times since September 2017, and has an average time of 20 minutes to complete.
That way, you can sort it not only by volume, but also by average time to complete / total time consumed, etc.