Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Indicator only matching breakdown sometimes

Oggman13
Tera Contributor

Hoping someone with a GigaBrain can assist.

 

I've got an automated indicator running against the sys_history_line table. Has a very specific query to only grab User.Department = GroupIWant, Field = assignment_group, Old value = GroupIWantAssignment group and then either Update time on Today or Created on Today.

If I run my collection jobs with 'Created on Today' my breakdown's / breakdown source / breakdown mapping matches it all up nicely and I get my scores in the right spot in my score sheet. Downside is I get a bunch of values that didn't really happen today, but the sys_history_line was 'created' that day by a later update on the job. If I set it to 'Update time on Today' (Which when I preview the indicator source or do it manually in a list view is the information I'm after) I only get unmatched results. If I pop a 'Created on Today && Update on Today' as the time condition, I get matched scores. I get the same result if I run the 'historic' job I set up to initally get some data, behaves if created is a condition / doesn't if I remove it.

Scoresheet Comparison.png

 

The downside is both when I preview the condition and build the same query in a list view of sys_history_line I seem to arbitrarily be missing a couple records.

 

sys_history_line condition returns.png

For the LIFE of me I cannot figure out why I get two different values, if I review my 'Update Time = Today" only list all the created dates match the day of the update time. When I dig into one of the records missing from the other they look identical to the ones that are populating correctly.

 

Does anyone have any insight on:

  1. Why if I set my indicator source to "Update time = Today" only it gives me unmatched records
  2. Why on EARTH "Update Time = Today" vs "Update Time = Today && Created = Today" misses some records
  3. (Slightly unrelated) Is it better if the 'created' date appears to update so often to have the daily job run at 11pm 0day - 0 day ago OR run it at 1am with the 1day - 1day ago schedule. I understand its not best practice to do reporting on a sys_ table like this, but its the only way to capture the exact stat business is after. 

Please save me from this

3 REPLIES 3

Oggman13
Tera Contributor

If it helps we're currently on Washington 7a.

jeffrubinoff
ServiceNow Employee
ServiceNow Employee

I have been documenting Performance Analytics for 7+ years, and I don't get this, either. Have you raised a Support ticket?

I haven't yet. I'm going to see over the weekend if I can replicate either problem in my PDI first to make sure its not some quirk of our instance. Just tough without all of the lovely records / PA components I've already buit.