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
There's code within RaygunRequestMessage.cfc that truncates everything but the first 4096 characters of the rawData.
For the project I'm working on I've increased this value to 32768 as it was truncating most of the payload from our api.
Can this truncation be safely removed from code?
The text was updated successfully, but these errors were encountered:
I'll need to double-check with someone from the team, @neiloflions. There is a limit on the overall payload that can be sent in one push to RG, but I'm not 100% sure if that breaks down into particular fields.
Sorry for the late followup. The 4096 character limit is our default limit when capturing raw data from a request body. This is the same limit we have in our .NET SDKs.
The intention behind this is to avoid automatically capturing too much information resulting in the error report being rejected by our API for being too large. We have max error report limit of 128kb, if over this limit it will be rejected by our API.
We are open to providing ways of increasing this limit. Perhaps a way of setting the desired limit with a default of 4096 still in place. Please feel free to open a pull request if you wish and we can consider this further.
Hello
There's code within RaygunRequestMessage.cfc that truncates everything but the first 4096 characters of the rawData.
For the project I'm working on I've increased this value to 32768 as it was truncating most of the payload from our api.
Can this truncation be safely removed from code?
The text was updated successfully, but these errors were encountered: