You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure that “silently truncating the dimension set” to an acceptable size is the best solution, but in any case the MAX_DIMENSIONS should be reduced to 9.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! Definitely open to proposals on how to treat this. I've considered adding a configuration parameter that would throw exceptions or to log and silently move on in these kinds of cases.
Based on the Zen of Python (“Explicit is better than implicit”, “Errors should never pass silently unless explicitly silenced”, and all that) I would say that throwing an exception is probably the right default behavior.
Per the upstream docs:
Currently, you're setting
MAX_DIMENSIONS
to 10:aws-embedded-metrics-python/aws_embedded_metrics/constants.py
Line 15 in 658b2eb
… and then using that to truncate the dimension set to 10 entries when serializing, e.g.:
aws-embedded-metrics-python/aws_embedded_metrics/serializers/log_serializer.py
Lines 23 to 30 in 658b2eb
I'm not sure that “silently truncating the dimension set” to an acceptable size is the best solution, but in any case the
MAX_DIMENSIONS
should be reduced to 9.The text was updated successfully, but these errors were encountered: