Why the Metric Definition wont auto-execute and auto-generate based on its frequency defined?

ChuanYanF
Tera Guru

Dear experts,

 

I have created a metric definition and defined its threshold but after I execute which i defined the frequency as daily to test it out, why will it not auto-generate metric data task, like how the metric will auto-generate by the frequency level and the metric definition does not. I do not plan to use metrics since its a dual interface, but I plan to show everything under metric definition only. Like the examples below:

ChuanYanF_0-1745474616543.png

 

1 ACCEPTED SOLUTION

Yes, the execute button on the metric definition is to execute all the metrics, and the one on the metric is just to execute for that specific metric. Now, if the metrics have already executed as part of the scheduled job execution, then nothing will happen, since it has already executed for that time period.

 

-Vaisakh

View solution in original post

3 REPLIES 3

Vaisakh Krishna
ServiceNow Employee
ServiceNow Employee

Hi,

 

Can you explain a bit more? It is unclear. The metric data tasks are auto-generated for each metric based on the frequency.  Say you have a Metric definition of type KPI and 'Daily' frequency, and it has 2 metrics, M1 and M2. Each day, 2 metric data tasks will be auto-generated for M1 and M2 respectively. The metric data tasks are tied to the metrics and not the metric definition.

 

Thanks,

Vaisakh

Hi Vaisakh, 

Thanks for your reply, my client would like to just use one interface level to create a metrics so either metric definition or metric since metric cannot be created without a metric definition, so we decided to just use the metric definition and execute the metric data task from there. So does that mean the execute button is just to execute all the metrics tied to this metric definition rather than act like the execute function in the metric where a metric data task will be created?

Yes, the execute button on the metric definition is to execute all the metrics, and the one on the metric is just to execute for that specific metric. Now, if the metrics have already executed as part of the scheduled job execution, then nothing will happen, since it has already executed for that time period.

 

-Vaisakh