
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2016 07:36 AM
Hi All,
Does anyone run data collections at an increased frequency?
A repeat interval that means that data is even more real time and gives insight to the latest operational scores? Is there any negative implication for the ServiceNow instance if jobs were run every 60 mins for example?
regards,
Andrew
Solved! Go to Solution.
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2016 01:57 AM
>Is there any negative implication for the ServiceNow instance if jobs were run every 60 mins for example?
Not necessarily, it depends on the collection: does it take more than 60 mins to collect? Yes, than it could have an impact. But when the score for an indicator is collected, it does not use more resources than running a report.
A few considerations:
-limit the indicators for which you want intraday collections
-indicators that use scripts are usually query-expensive to run
-consider if you need to collect all breakdown values on an intraday schedule as well
-be sure to set the relative start and end in your job correctly; if your indicator source contains opened/resolved on/after today, use '0' for both start and end
-keep your 'default, daily' job for the indicator as well, so the final score for today is still collected tomorrow (read again 😉 )
-if your indicator is a 'count' aggregate and you just want to show the number as a single score in a widget, consider to use the single score auto-refresh reporting widget Enable real-time updating for single score report widgets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2016 01:57 AM
>Is there any negative implication for the ServiceNow instance if jobs were run every 60 mins for example?
Not necessarily, it depends on the collection: does it take more than 60 mins to collect? Yes, than it could have an impact. But when the score for an indicator is collected, it does not use more resources than running a report.
A few considerations:
-limit the indicators for which you want intraday collections
-indicators that use scripts are usually query-expensive to run
-consider if you need to collect all breakdown values on an intraday schedule as well
-be sure to set the relative start and end in your job correctly; if your indicator source contains opened/resolved on/after today, use '0' for both start and end
-keep your 'default, daily' job for the indicator as well, so the final score for today is still collected tomorrow (read again 😉 )
-if your indicator is a 'count' aggregate and you just want to show the number as a single score in a widget, consider to use the single score auto-refresh reporting widget Enable real-time updating for single score report widgets