Allow `LOG_STRING_TRUNCATE_LENGTH` to be configurable

[andrewalc]

New Feature / Enhancement Checklist

• [x] I am not disclosing a vulnerability.
• [x] I am not just asking a question.
• [x] I have searched through existing issues.

Current Limitation

Currently there is no way to reconfigure the LOG_STRING_TRUNCATE_LENGTH threshold for when a parse log is truncated. It's currently set to truncate when a log exceeds 1000 characters. This affects parse trigger logs and parse cloud function logs that use truncateLogMessage

Feature / Enhancement Description

There should be a server option to set LOG_STRING_TRUNCATE_LENGTH to a length other than 1000 characters. Perhaps even an option to disable truncation altogether. The default threshold should remain 1000 characters if not set in server options.

Example Use Case

• Security measures where the capture of full un-truncated logs is critical
• Easier troubleshooting / debugging with parse logs that exceed 1000 characters

Alternatives / Workarounds

There is currently no way to disable or change LOG_STRING_TRUNCATE_LENGTH for parse server logs

3rd Party References

[parse-github-assistant[bot]]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!