Anomaly detection checks not showing as freshness policy in UI

[brandonpeebles]

What's the issue?

After adding the anomaly detection freshness checks for my dbt assets, the checks correctly appear in the checks tab of the assets, but they aren't being tagged as "freshness" checks or policies. This means that it will appear as if the asset has no freshness policy even though a failing check is the anomaly detection freshness check. For example, one of the failing checks below is the anomaly based freshness one, but I wouldn't know that until clicking into the asset as it's just treated as any other check would be.

What did you expect to happen?

I would expect Dagster to say a freshness policy is defined (ideally noting that it's dynamically generated vs hardcoded) and for assets failing the freshness check to appear in the tab for freshness.

How to reproduce?

Added code as described in documentation here to build freshness checks: https://docs.dagster.io/guides/test/data-freshness-testing#anomaly-detection

Dagster version

1.10.19

Deployment type

None

Deployment details

Hybrid deployment

Additional information

Additional feature request: if an anomaly based freshness check is warning/failing in the UI, it would be great if we could ignore it via the UI as well to help train the model

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.