Indicators for Monthly Data

oana5 · ‎04-12-2016

Hello everyone!

I want to create an indicator to show the number of active problems monthly.

I am not sure if is it ok to use Monthly frequency and Daily Data Collector Job? Or should I create a Data Collector Job and scheduled it to run monthly?

Thank you in advance!

Oana

pieter_goris · ‎04-12-2016

Oana,

I assume that with 'an indicator to show the number of active problems monthly' you are looking for the number of not-closed problems at the end of the month. If so, you can use two approaches.

But first of all, try to use conditions that are not based on states but on dates (active = true is based on states). This will allow you to collect accurate historic scores values as well. So whenever you need to recollect scores, the indicator (source) is set up correctly.

First approach: your indicator source should look like:

The 'Today' in the conditions above are placeholder for real dates. The real dates are put in when the scores collection runs.

Set up your scores collection job like:

ad1: run your collection on a monthly schedule on the first day of the (next) month. (With above settings, it must be on the 1st day of the month)

ad2: set your collection parameters to go back 1 day: so if you run this on April 1, the Today in the indicator source conditions gets replaced by real dates and reads like (simplified):

Opened on March 31 OR

Opened before March 31

AND

Closed is empty OR

Closed after March 31

If wanted you could use the same indicator source also in weekly or daily collections. It requires separate weekly and daily jobs with different Job parameters (weekly/daily) but with the same Collection parameters

Second approach: you can also set up a different indicator source like:

Now your scores collection job should look like:

So in the Collection parameters set the relative start and end to 0, meaning today.

Now on the Job parameters you can run this on any day of the month, if you use dates in your conditions! *

Of course, this indicator source is only fit to be used in monthly collections!

*if you use states and you run the scores collection job on the 7th of the month, than problems that are set to not-active on the 1st - 6th day of the month are not included in your score, but they should be.

Hope this helps.

Cheers, Pieter

View solution in original post

Nomava Ntaka · ‎04-17-2019

What is the best approach here, I have the same issue.

how do I present my widget correctly here.

Robin Hearne · ‎07-01-2019

I adapted Peter's approach to make sure that the data is being shown for the appropriate month.

I created a Monthly Indicator Source to capture all tickets (HR Case in my case) that occured on or before the current month and were closed after the current month:

Then for the Data Collection job I used daily job with a scripted condition to ensure that the job only runs on the last day of the month: