It looks like the batch metric API fails when we are requesting 500 or more metrics. This has been noticed while checking the feature branch for the DDS resource from dvelop.
After a long time of trial and error for the bug, I discovered, that it is related to the number of elements requested. To make it clearer, that this is related to the number of elements and not because of the metrics. With different metrics inside this did not work.
It looks like the batch metric API fails when we are requesting 500 or more metrics. This has been noticed while checking the feature branch for the DDS resource from dvelop.
My first guess was that the request might be larger than 512KB which was not the case. The 512KB are mentioned in the official docs for the batch metrics: https://docs.otc.t-systems.com/cloud-eye/api-ref/api_description/monitoring_data_management/querying_monitoring_data_in_batches.html#ces-03-0034-table14755123118236
After a long time of trial and error for the bug, I discovered, that it is related to the number of elements requested. To make it clearer, that this is related to the number of elements and not because of the metrics. With different metrics inside this did not work.