Review this checklist before submitting. - [x] GitLab issues are for bug reports and feature requests. If this is a help request, post on [Gitter](https://gitter.im/GlitchTip/community). If you have or want paid support, please use the chat widget on https://glitchtip.com. - [x] Document reproduction steps. Be as detailed as possible. - [x] If applicable, try to reproduce the problem on https://app.glitchtip.com - [x] Be considerate of the reviewer of your issue and their time. They are likely unpaid. GlitchTip is open source and comes with absolutely no warranty. - [x] Check existing issues first. :thumbsup: the issue to show interest. - [x] Do not open issue related to automated security scanners or other static anaysis tool. We use Renovate and GitLab for this. Instead, ask on [Gitter](https://gitter.im/GlitchTip/community) how you can help get involved in the project and make the changes you wish to see. ## Description Currently, Slack notifications sent by GlitchTip (for both errors and uptime monitoring) are not very informative at a glance. The main message text is typically generic, such as "GlitchTip Alert" or "GlitchTip Uptime Alert". This is because the actual, useful alert details are placed inside a webhook attachment field. As a result, Slack's channel list and push notifications only show the generic text, forcing users to click on the message to see what the alert is actually about. ## Proposed Solution(s) To make these notifications immediately actionable, I propose moving the detailed alert message from the attachment field into the main text field. The "GlitchTip Alert" prefix in the text field is redundant. The Slack webhook integration itself is (in most cases) already configured with a name and icon (e.g., "GlitchTip"), which clearly identifies the source of the message. By putting the specific error or warning message in the text field, it will be instantly visible in the Slack channel list and in push notifications, providing immediate context to the user.