Monthly Job/Indicator calculating from first day of previous month, not last

[Chris W1]

Hi Everyone,

Hopefully this is me making a basic error and not being able to find it, hope someone can help me find it.

I'm creating a monthly metric on the number of incidents that are more than 14 days old at the end of the month but when i run the collection job, it' using the first day of the month to count back the 14 days from and hence is moving the scores back by one month, so for example, the records for "February" are showing incidents that were more than 14 days old on 2/1, not on 3/1. 

Here's my indicator source:

And here's my collection parameters in the job:

And here's a view of the records collected for February, showing that the 14 days being used is from 1/31, not 2/28:

I've tried applying the 14 condition on the indicator not the indicator source, that didn't make any difference to the outcome. I've tried a myriad of different combinations of relative start and end dates with no different outcome either

If anyone can tell me how to get this to use 3/1 instead of 2/1 as the February date, I'd be incredibly grateful. Thanks.

(Also open to workarounds like grabbing a daily score from the last day of the month and automating dumping that into a manual indicator, because doing that manually is my current backup plan.)

[D Dollbaum]

Have you tried making the "relative start" zero months ago?  Is that allowed?

[Chris W1]

I tried that (I'm in a sub-prod instance here) but it didn't make any difference, unfortunately. (also I think there's best practice reasons not to do that, IIRC)

[Chris W1]

@Adam Stout @Thomas Davis apologies for the potentially rude use of the tag system here, but wondering if you would have any ideas on this one please?

[Adam Stout · Accepted solution]

I can see a few options

• Run this daily then use a formula indicator to only display the value from the last day of the month. I think we covered this in an Analytics Academy on advanced formulas.
• Potentially report on SLAs duration instead of the incident themselves.  Then the query won't care about the date (although the time the job runs is very important now).