Why Dynatrace API accept agregationType parameter instead of aggregationType parameter for value percentile ?

sjoly — Tue, 25 May 2021 14:12:26 GMT

Hi, it's not really a question more to inform or investigate about the reason why.

About this great and helpful article of Wolfgang Beer : Custom percentiles for dashboard charts & Dynatrace API calls.

In the example API call fetches url the name parameter agregationType with only 1 g works for the value percentile. But for other Built-in metrics and aggregations, agregationType parameter with only 1 g don't works and will return the message :

{
    "error": {
        "code": 400,
        "message": "The aggregation type is not allowed for the given timeseries id."
    }
}

So be careful to always use aggregationType with 2 g because it always works 🙂

I hope this will help some of you to not loose time, as me 🙂

Re: Why Dynatrace API accept agregationType parameter instead of aggregationType parameter for value percentile ?

wolfgang_beer — Mon, 15 Oct 2018 06:16:21 GMT

Hi Stephane,

Thanks a lot for reporting that. We will immediately fix the typo in the blog post.

Best greetings,

Wolfgang

topic Why Dynatrace API accept agregationType parameter instead of aggregationType parameter for value percentile ? in Dynatrace API

Why Dynatrace API accept agregationType parameter instead of aggregationType parameter for value percentile ?

Re: Why Dynatrace API accept agregationType parameter instead of aggregationType parameter for value percentile ?