Lukas Steger
06/03/2026, 5:48 AMkapa.ai
06/03/2026, 5:48 AMalerts_v2 table, but the information stored is limited:
What alerts_v2 does store:
⢠A sent_at timestamp recording when an alert was dispatched
⢠A status field (e.g., pending, skipped, sent)
⢠Rich alert context in a data JSON column (test ID, table/column names, severity, owners, tags, etc.)
[alerts_v2 structure]
What it does NOT store:
The knowledge sources do not mention any storage of a direct Slack message URL (e.g., a https://slack.com/archives/... permalink) for sent alerts. There is no reference to Elementary capturing or persisting the Slack message URL after delivery.
This aligns with the general pattern described ā Elementary marks alerts as sent and records sent_at, but the integration is one-directional (push to Slack) with no apparent callback to store the resulting message URL. [alerts_v2 structure]
If storing a reference back to the Slack message is important for your use case, this would likely need to be implemented as a custom integration outside of Elementary. š 0 button š 0 button ā¹ļø Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.