Closed jhackshaw closed 5 months ago
I am generally in favor of this change, but want to call out a few risks related to overwriting default attributes:
While it is currently possible to make these mistakes, this change makes it easier to make these mistakes. The tradeoff is that it provides more flexibility for CloudWatch RUM users, especially where feature gaps exist such as for app monitors that monitor multiple top-level domains.
question: where do we enforce the 10 custom attribute limit? Does changing default attributes count towards that limit?
Eg - I change all the default attributes. Can I add 10 more custom attributes?
question: where do we enforce the 10 custom attribute limit? Does changing default attributes count towards that limit?
Eg - I change all the default attributes. Can I add 10 more custom attributes?
There is no change to the 10 custom attribute limit. Default attributes do not count towards the limit even if they are overwritten.
As far as I can tell, the web client does not enforce any limits. This is all done by the service.
Allow the customization of default attributes, excluding the
platformType
.Primary use case is overriding the domain reported to RUM to facilitate using the same app monitor across different top-level domains which is not natively supported in RUM configuration.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.