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
The fixed value of 2048 could be rather limiting. Is there a technical issue, to capture bigger bodies?
If I'm not misstaken, the java client has a bigger limit here.
It would be really nice, if this would be a config parameter for the client.
The text was updated successfully, but these errors were encountered:
Is there a technical issue, to capture bigger bodies?
No there isn't - by looking at the PR which introduces it, it seems it was an arbitrary choice. We definitely want limit this and not capture super long bodies, but the 2k limit isn't based on some specific thing.
If I'm not mistaken, the java client has a bigger limit here.
Correct, they use a 10K limit.
It would be really nice, if this would be a config parameter for the client.
So, as a next step I opened #1368 - if that gets merged the limit will be 10K in the next release.
I also leave this open and try to propose a cross agent setting to give users the option to change the limit. (fyi: if we introduce a setting then preferably we'd do that across all agents and not just for .NET).
The fixed value of 2048 could be rather limiting. Is there a technical issue, to capture bigger bodies?
If I'm not misstaken, the java client has a bigger limit here.
It would be really nice, if this would be a config parameter for the client.
The text was updated successfully, but these errors were encountered: