<@U088WCP3B4P> is there a way to add a description...
# ask-elementary-ai
j
@kapa.ai is there a way to add a description to a volume anomaly test that is performed twice over the same source for differents metrics?
k
A message from kapa.ai
Yes. Add a custom description via the meta block in your test definition. This works for Elementary anomaly tests and will show in the dashboard and alerts, helping you distinguish multiple tests on the same source. Example:
Copy code
yaml models:   - name: my_model     tests:       - elementary.volume_anomalies:           # config for metric A           meta:             description: "Volume anomalies for metric A (filtered X)"       - elementary.volume_anomalies:           # config for metric B           meta:             description: "Volume anomalies for metric B (filtered Y)"
(This pattern is confirmed for adding descriptions to Elementary tests via meta and is commonly used to differentiate similar tests in the report and charts.) ([Slack: add custom description](https://slack.com/archives/C02CTC89LAX/p1708443408220759); [Slack: descriptions in meta](https://slack.com/archives/C02CTC89LAX/p1697653387970259); [Slack: alias/title via description](https://slack.com/archives/C02CTC89LAX/p1705372587987189); [Slack: set description for tests](https://slack.com/archives/C02CTC89LAX/p1736818351146109))
j
@kapa.ai how about giving a name to test to make it more friendly to use and find into the report?
k
A message from kapa.ai
Short answer: not reliably for anomaly tests yet. - Custom names generally aren’t shown for Elementary anomaly tests (e.g., volume_anomalies/column_anomalies) in the report today; this has been a known limitation with open issues to improve it ([Slack: anomaly tests names not shown](https://slack.com/archives/C02CTC89LAX/p1697729858077339); [Slack: report name vs console name](https://slack.com/archives/C02CTC89LAX/p1696829659325819); [GitHub issue 1224 reference](https://github.com/elementary-data/elementary/issues/1337)). - Workaround: add a descriptive meta.description to each test; this appears in the dashboard and alerts and helps differentiate similar tests ([Slack: use meta.description](https://slack.com/archives/C02CTC89LAX/p1708443408220759); [Slack: meta for anomaly tests](https://slack.com/archives/C02CTC89LAX/p1697653387970259); [Slack: labeling charts via description](https://slack.com/archives/C02CTC89LAX/p1705372587987189); [Slack: example with column_anomalies](https://slack.com/archives/C02CTC89LAX/p1736818351146109)). Example:
Copy code
yaml - elementary.volume_anomalies:     # your config...     meta:       description: "Friendly label for this volume anomaly test"