Basic indicators not showing up to date score data for 19/08 (yesterday)?

acrascall
Kilo Expert

New to PA - only had plugin activated in our fuji configuration this week.   The basic indicator is not showing me score data for 19/08 for 'number of resolved incidents' and 'incident backlog growth' but is for number of new incidents and number of open incidents?

See enclosed screen shot - is there any reason I cannot see yesterdays activity around resolution and as a consequence backlog?

1 ACCEPTED SOLUTION

Hi Andrew,



Increasing this threshold doesn't solve the problem. Question: hy did you run the historical job this morning? The historical job should run only once. After this collection turn on the daily job and that's it.


The error however does ring a bell to me. The indicator incidents.resolved should only count the number of incidents resovled on yesterday, not all incidents ever resolved. Could you please check the following?


Go to Indicator sources -> Incidents.resolved


it should look like this:


incidents.resolved.PNG



Now check the number of records matching your condition. This is probably a very large number. If that's the case try adjusting the condition to the following:



incidents.resolved-or-closed.PNG


Now click on the double yellow arrows to see if the number drops.


Verify you have only selected incidents resolved on today by click on the blue text.



Click update if correct.


Now run your historical data collection once more to update the historical values.



Cheers,


Vincent


View solution in original post

7 REPLIES 7

Thanks Vincent, the historical data collector has been run a few times as I was tweaking the indicator source to match our instance.   The resolved Incidents indicator though was looking at all historical resolved Incident instead of those just resolved today.   Will rerun historical and then the daily collector again and check on results.


Hi Andrew,


That's great to hear! Could you close this post marking my reply as correct answer? Tnx.



Cheers,


Vincent


acrascall
Kilo Expert

The errors looked linked to a threshold:



"Fetched too many rows from indicator source Incidents.Resolved. Allowed: 50,000 fetched: 132,593"



Are there any performance issues if the threshold is increased and the job data collectors re-run?   What threshold is utilized within your own instances?