This is a fix for a bug I introduced when truncating responses - turns out it returned the truncated response to the caller, resulting in deserialization errors. Whoops.
I tested this in our dev environment and while it fixed the issue with large responses from Elasticsearch, the trace does not show up on the Epsagon side. Not sure why that would be, perhaps an issue with the truncated response? I've attached a debug of the final trace that was sent.
trace.json.txt
This is a fix for a bug I introduced when truncating responses - turns out it returned the truncated response to the caller, resulting in deserialization errors. Whoops.
I tested this in our dev environment and while it fixed the issue with large responses from Elasticsearch, the trace does not show up on the Epsagon side. Not sure why that would be, perhaps an issue with the truncated response? I've attached a debug of the final trace that was sent. trace.json.txt