Problem with indicator score

Go to solution
ashtiw
Kilo Contributor

‎01-19-2018 02:03 AM

Hello,

I have created an indicator and when running a job against it, it distributes the total count of an incident across each month, meaning it displays somewhat the same values across each month. Below are the additional information:

Indicator Source condition:

Business Service Parent Parent = Auto - Business Line .and.

Opened on Today .or.

Opened < 01-19-2018 00:00:00

Indicator:  

No additional condition

Job:

Relative Start : 1 week ago

Relative End : 1 days ago

Issue:

1. Indicator Score is distributing the total count of incidents starting from 11-05-2015 20:19:07 till yesterday. Ideally, it should have just distributed the total count of incidents opened in the last week.

2. Why scores are not distributed by daily count ? Below snapshot for ref.

3. What changes should I make to see the daily distribution of incident count ?screenshot 2.PNG

screenshot of scoresheet.PNG

Any suggestion will be appreciated.

Regards,

Ashish

Labels:
Preview file
20 KB
Preview file
59 KB
Preview file
19 KB
0 Helpfuls
  • 2,077 Views
1 ACCEPTED SOLUTION

Go to solution
Josh Cooper
ServiceNow Employee
ServiceNow Employee

‎01-19-2018 07:55 AM

Remember those indicator score conditions are going to be run the same way each day.  



Think of it like this - a PA job will go backward, a day at a time, and execute the conditions from the Indicator Source (to build a temp table) then the conditions from the indicator against the temp table it creates.



So with your condition (not knowing actual numbers), you're always going to get the sum of all the incidents created before Jan 19th, for every day, PLUS whatever tickets happened on that day.     It'll climb a day at a time until January 19th, then level off for the most part, with the difference you see being the difference in tickets from one day to the next.



I.e.   If all of the tickets that exist before the 19th were 1700, then you open 90 on Jan 20th, then the 20th would show 1700+90.   On the 21st you have 80 new tickets, so the value would be 1700+80 (because the 90 from the 20th don't match the criteria).



You probably really just want to say "Created on Today" - which means 'This Day" to Performance Analytics, so when the job runs, the score you see will be those tickets created for THAT SCORE day.   Then if you pick a "by week sum+" time series (the plus means show the partial week as well).   Then it'll add all the scores together for the week and graph that.



Alternatively, if you want the score to literally include all the tickets from the last week, collected daily, then you can choose "Created on Last 7 Days" or "Created on This Week" depending on whether you want literally only this week, or 7 days prior from any day.   Note that when you do this, your 'By Week Sum+" won't give you an accurate number, because you'll be counting the same tickets multiple times.   Still useful as a trend, but not as an actual count.


View solution in original post

0 Helpfuls
2 REPLIES 2

Go to solution
Josh Cooper
ServiceNow Employee
ServiceNow Employee

‎01-19-2018 07:55 AM

Remember those indicator score conditions are going to be run the same way each day.  



Think of it like this - a PA job will go backward, a day at a time, and execute the conditions from the Indicator Source (to build a temp table) then the conditions from the indicator against the temp table it creates.



So with your condition (not knowing actual numbers), you're always going to get the sum of all the incidents created before Jan 19th, for every day, PLUS whatever tickets happened on that day.     It'll climb a day at a time until January 19th, then level off for the most part, with the difference you see being the difference in tickets from one day to the next.



I.e.   If all of the tickets that exist before the 19th were 1700, then you open 90 on Jan 20th, then the 20th would show 1700+90.   On the 21st you have 80 new tickets, so the value would be 1700+80 (because the 90 from the 20th don't match the criteria).



You probably really just want to say "Created on Today" - which means 'This Day" to Performance Analytics, so when the job runs, the score you see will be those tickets created for THAT SCORE day.   Then if you pick a "by week sum+" time series (the plus means show the partial week as well).   Then it'll add all the scores together for the week and graph that.



Alternatively, if you want the score to literally include all the tickets from the last week, collected daily, then you can choose "Created on Last 7 Days" or "Created on This Week" depending on whether you want literally only this week, or 7 days prior from any day.   Note that when you do this, your 'By Week Sum+" won't give you an accurate number, because you'll be counting the same tickets multiple times.   Still useful as a trend, but not as an actual count.


0 Helpfuls

Go to solution
ashtiw
Kilo Contributor
In response to Josh Cooper

‎01-22-2018 07:21 AM

Thanks a lot Josh. So, ideally case would be:



Opened on "Today" in the indicator source and then extracting the data by the job.. right ?


0 Helpfuls