Allow title truncation to be disabled or configured in Slack integration

[sgrimm-sg]

Summary

When a notification is sent to Slack via the Slack integration, the title is always truncated to 40 characters and the culprit is included in its entirety. Add a way to either disable title truncation entirely or set the limit to something higher than 40.

Motivation

For some applications, the text of an error is far more useful for initial troubleshooting than the culprit is. For example, in a Java application, I might have code like

log.error("Unable to contact service for destination {}", destinationId);

The Slack notification title gets rendered as,

Unable to contact email service for destinatio - com.mycompany.myservice.common.client.email.aws.AmazonSESClient

In this case the destination is the thing I want to know if I'm monitoring an alerts Slack channel, but it is cut from the Slack message in favor of the fully-qualified class name, which has no length limit.

If the total length of the title has to be limited, I'd much rather lose the package name, or even the entire class name, than any of the message.

The truncation is happening here:

sentry/src/sentry/integrations/slack/utils.py

Line 77 in 259f996

return u'{} - {}'.format(group.title[:40], group.culprit)

[BYK]

Closing this issue due to staleness. Feel free to comment here if you think we should still work on this.

[robertpranjic]

very much needed by our company, +1

[davidwernerhh]

I think this is an important issue and 40 characters are just not that much really +1

[CevinEichnau]

same here. need is there +1

[joeyaurel]

I am also for that the truncation should be removed or be configurable.

I assume that the following line would also be affected by this change:

sentry/src/sentry/integrations/slack/utils.py

Line 71 in 259f996

return u'{} - {}'.format(ev_metadata['type'][:40], group.culprit)

[davidjung1977]

we really need this +1

[BYK]

Reopening to measure interest and see if we can get this done. PRs also accepted as this seems not too hard.

[AngelGris]

I believe this one was fixed in PR 14464

[Pavankumardontha]

@BYK is this still open ? Can i contribute ?

[hubertdeng123]

You can contribute whenever you'd like. Seems like this is no longer an issue though

[Pavankumardontha]

Thanks @hubertdeng123 for your reply. Will work on this.