Introduce config for MAX_STRING_LENGTH

[puittenbroek]

Problem Statement

In our on-premises Sentry, we're regularly missing some context information (variables, part of variables) in our issues. This is quite annoying since they usually contain ID or hashes that we need to further debug the information.
We want to raise the limit that the Sentry SDK sends. But that limit is hard coded.

There is a nice TODO, saying it should be read from config, but I cannot find any issues regarding that.

So the only solution would be monkeypatching this value. Which I consider the source of (all) evil and should be avoided, especially in production environment.

Solution Brainstorm

1. Introduce a config for MAX_STRING_LENGTH
2. Read MAX_STRING_LENGTH from said config
3. Optional: Document said config with a disclaimer that you can/will break Sentry internals if you raise this limit to a too high value (assumption, I'm sure it's set to it's current value for a reason)

[antonpirker]

Hey @puittenbroek !

Sounds like a good suggestion.
What do you think, do you want to give it a go and submit a PR?

[puittenbroek]

I'll try and squeeze it in between things :)

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[puittenbroek]

Spent some time on a PR, let me know what you think.

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[puittenbroek]

Bump