Hello <@U088WCP3B4P>! At the start elementary sen...
# ask-elementary-ai
e
Hello @kapa.ai! At the start elementary sent very detailed test failures alerts to Slack, but now they're more limited. Please note that no config change has been made. e.g. before we had things like the Test Results Sample, Test Results Query etc., now only the name of the test that failed
k
A message from kapa.ai
Hello! Based on the knowledge sources, there are a few reasons why your Slack alerts from Elementary may have become less detailed, even if you haven't changed your configuration: 1. Grouped Alerts Reduce Detail If you are running
edr monitor
with the
--group-by table
option (or have set
slack_group_alerts_by: table
in your model/test meta), the alerts will be grouped by table. Grouped alerts intentionally contain less information per issue—typically just a list of failures, without detailed fields like test results samples or queries. This is expected behavior and is documented as such. If you want more detailed alerts, try running without the group-by option or removing the
slack_group_alerts_by
meta field from your configuration. Regular (non-grouped) alerts include all fields by default, unless otherwise configured [Oss Alerts Configuration](https://docs.elementary-data.com/oss/guides/alerts/alerts-configuration#alerts-distribution) [Slack thread](https://slack.com/archives/C02CTC89LAX/p1678315604138639). 2. dbt 1.8 and
data_tests
Change
If you recently upgraded to dbt 1.8, note that dbt changed the way tests are defined (from
tests:
to
data_tests:
). There are open issues indicating that this change may have broken the attachment of config and alert fields, including
test_results_sample
, in Elementary. This could explain why detailed fields suddenly disappeared after an upgrade, even if you made no config changes yourself [Github Issue #1692](https://github.com/elementary-data/elementary/issues/1692). 3. Alert Fields Configuration Elementary allows you to customize which fields appear in alerts using the
alert_fields
meta property. By default, all fields are included, but if this was changed (even unintentionally), it could limit the details shown. However, you mentioned no config changes, so this is less likely unless there was an indirect change (e.g., via package upgrade defaults) [Oss Alerts Configuration](https://docs.elementary-data.com/oss/guides/alerts/alerts-configuration#alerts-distribution). 4. Known Bugs or Upgrades There have been bugs in certain versions of Elementary that affected alert content (e.g., missing samples, duplicate alerts, etc.). If you recently upgraded Elementary or dbt, you may be affected by such a bug. Check the release notes or open issues for your current version [Github Issue #1692](https://github.com/elementary-data/elementary/issues/1692). What to do next: - Check if you are using grouped alerts (
--group-by table
or
slack_group_alerts_by: table
). If so, try disabling this to restore detailed alerts. - If you recently upgraded dbt or Elementary, review open issues and consider downgrading or applying any available patches. - If none of the above applies, there may be a new bug or regression—consider opening a GitHub issue with your details. Let me know if you need help checking your configuration or troubleshooting further!