topic Re: Null Values in API Timeseries in Dynatrace API

Null Values in API Timeseries

rb0c70091 — Wed, 26 May 2021 11:42:05 GMT

We are getting Null and 0 values returned when accessing some metrics like com.dynatrace.builtin:app.jserrorsduringuseractions in the timeseries API. Is this because the "action", in this case was not seen during, the polling period, so no value is recorded, rather than the "action" happening and 0 errors being seen?

Re: Null Values in API Timeseries

hayden_miedema — Fri, 15 Dec 2017 19:24:06 GMT

Hi Ray,

Your explanation is exactly correct. If no user actions are seen in that time period you will get a null value. If there are actions, but no errors (in your case based on the metric) you will see a 0 reported.

HTH,

Hayden

Re: Null Values in API Timeseries

rb0c70091 — Sun, 17 Dec 2017 15:14:30 GMT

@Hayden M Thank for that Hayden but if this is the case why are there Null values on metrics
like com.dynatrace.builtin:app.errorcount or
com.dynatrace.builtin:app.useractions ? if none are seen should
this not be 0 ?

Re: Null Values in API Timeseries

wolfgang_beer — Mon, 18 Dec 2017 07:48:43 GMT

Null within the timeseries API means 'no data'. In case of errorcounts a zero means that we observed some user actions during that minute and none of those had an error attached. So the result is '0'. On the other hand if we do not see any user action within a timeframe we do state 'null' as no data available for that timeframe.

In case of the metric 'com.dynatrace.builtin:app.useractions' that seems a bit strange I agree as the value '0' can't happen. Either we observe a user action then the value is above zero or we do not observe any then the value is 'null'.

Re: Null Values in API Timeseries

rb0c70091 — Mon, 18 Dec 2017 08:07:37 GMT

Thanks Wolfgang.