Current State:

Compass currently delivers alert payloads that are often large and contain a significant amount of bundled information. The payloads are not always structured in a way that makes it easy for engineers to quickly identify the most critical details. As a result, teams must sift through unstructured messages, which increases cognitive load and slows down incident response, especially when alerts are consumed in Slack.

Proposed Future State:

Enable users to dynamically edit or customize the Compass alert payload template before it is sent to third-party integrations like Slack. This would allow teams to highlight only the most relevant data, present alerts in a streamlined and structured format, and reduce noise. The result would be improved readability, faster response times, and a more efficient and reliable alerting workflow.

Alternative (e.g. Third Party Plugin):

Currently, there are limited options for reshaping Compass alert payloads before they reach Slack. Some teams may attempt to use middleware or custom scripts to reformat payloads, but this adds complexity and maintenance overhead. A native solution within Compass would be more robust, user-friendly, and easier to maintain.