dynatrace limits uploads to 15k

[pjfanning]

I suggest that we can support a dynatrace.maxMessageSize property.

kontainers/micrometer-registry-dynatrace@48e27c7 has an implementation where if the limit is reached, the upload data is split over multiple messages.

[jkschneider]

Does dynatrace blow up if the 15k limit is exceeded?

[pjfanning]

Dynatrace rejects the message if it exceeds 15k with a HTTP 413 Payload Too Large response.

{"code":413,"message":"Entity must not be larger than 15360 bytes"}

[jkschneider]

Good to know. Is there any value then in making the max size configurable?

[pjfanning]

In kontainers/micrometer-registry-dynatrace@48e27c7 - I split the message into mutiple messages so that none exceeds the maxMessageSize.

[jkschneider]

@pjfanning Yep, implementation makes sense. Should we make the max size a config option though or hard code that? My biases lean me away from a config option simply so we aren't committed to that from an API surface area perspective. That is, unless there is some immediate reason why configurability is desirable.

[pjfanning]

I guess we could hardcode 15k. I can put together an MR in the coming days.