message too long errors about aws-xray-sdk-python HOT 7 CLOSED

Just for record: looks like in current version _max_subsegments can be publically changed by assigning to streaming_threshold property:

xray_recorder.streaming_threshold = 10

Also it is exposed as streaming_threshold argument to .configure() method.

from aws-xray-sdk-python.

Released as part of 0.96.

from aws-xray-sdk-python.

Hi, the SDK has thin layer modular design. The X-Ray recorder decides when to stream a segment (e.g. send out some closed children subsegments first) and the emitter simply executes what it is told to do. The default maximum number of subsegments it holds is set to 30: https://github.com/aws/aws-xray-sdk-python/blob/master/aws_xray_sdk/core/recorder.py#L46. The reason of using size of a subsegments array is that byte counting is expensive.

Depends on what do your segment look like 30 subsegments could still be large. You can modify it to a lower value so the streaming happens earlier and more frequent. This number is tested under UDP packet size 64KB but depend on your operating system configuration it might allow an even smaller packet pass through.

Hope it helps.

from aws-xray-sdk-python.

Close. Feel free to re-open for any additional comment.

from aws-xray-sdk-python.

I believe this is not configurable in xray-sdk, is this not the case? See https://github.com/aws/aws-xray-sdk-python/blob/master/aws_xray_sdk/core/recorder.py#L46

from aws-xray-sdk-python.

unfortunately I'm not allowed to re-open

from aws-xray-sdk-python.

Sorry about that. You are right. I confused it with our another SDK. The public interface configure() is missing a keyword argument for configuring this. Will add it to the next release. A PR is also welcome.

For workaround you can temporarily use xray_recorder._max_subsegments = 10 until the public interface is added.

from aws-xray-sdk-python.