Calculated service metrics - Response/Processing time unit

[Babar_Qayyum]

Dear All,

What could be the reason that the 'Response time/Processing time' unit fixed as 'Microsecond' in the calculated service metrics? Whereas, the same metric can be used with the different units in the custom events for alerting. The cluster version is 1.216.132.20210601-083338.

Regards,

Babar

[bobby_crumley · Accepted solution]

Hi Babar

This metric is captured by Dynatrace in the Microsecond granularity by default, and when reported that can be mathematically grouped and added to show minute/second/millisecond times. As calculated service metrics cannot be adjusted after creation, this ensures the most detailed granularity within this metric so it can be used. 

Because of this, this is a metric which can be used for Custom Alerting, and by changing the granularity it just tells the back end to group microseconds into mili/second/minute timings you are requesting. 

In short, it prevents a custom metric from creating per minute intervals and trying to make Custom Alerts in second intervals.

Hope this helps

Bob

[Babar_Qayyum]

Hello @bobby_crumley 

Thank you for your comments. Is this started recently or was it there since the beginning but I did not notice?

Regards,

Babar

[bobby_crumley]

Hey Babar, yes this has been since the beginning.

[Babar_Qayyum]

Hello @bobby_crumley 

Thank you for the confirmation.

Regards,

Babar