topic Re: About difference of available timeseriesId between Dynatrace SaaS and Managed in Dynatrace API

About difference of available timeseriesId between Dynatrace SaaS and Managed

kohei-saito — Fri, 01 Mar 2019 05:57:40 GMT

Hi,

are there 'timeseriesId' metrics for TimeseriesAPI available on only one of either Dynatrace SaaS or Dynatrace Managed?

For example, I can use "com.dynatrace.builtin:appmethod.useractioncount.load" for Dynatrace Managed Timeseries API, but cannot for SaaS.

With this metric, I got the 404 response from SaaS Server:

{
  "error": {
    "code": 404,
    "message": "Timeseries id com.dynatrace.builtin:appmethod.useractioncount.load is not valid"
  }
}

c.f.)

If you look at this page(https://www.dynatrace.com/support/help/shortlink/a...), you will find this metric on Managed but not on SaaS.

Regards,

Kohei Saito

Re: About difference of available timeseriesId between Dynatrace SaaS and Managed

wolfgang_beer — Fri, 01 Mar 2019 07:11:27 GMT

That one is easy to explain, Dynatrace SaaS release cycle is 2 releases (~4weeks) ahead of Dynatrace Managed. That is the reason why in some cases an id can be already available in Dynatrace SaaS while it will be available 4 weeks later in Dynatrace Managed. Dynatrace SaaS and Dynatrace Managed are identical from codebase and feature set, its just because of the release cycle.

Best greetings,

Wolfgang

Re: About difference of available timeseriesId between Dynatrace SaaS and Managed

kohei-saito — Fri, 01 Mar 2019 07:25:25 GMT

I see, that makes sense.

Dynatrace Managed is released in advance of SaaS, so some of available metrics in Managed may not be available in SaaS.

Thank you very much!

Kohei