Itamar Hartstein

Closing since I believe [this PR ](https://github.com/elementary-data/dbt-data-reliability/pull/665/commits) fixed this issue. Please re-open if relevant!

Hi @kokorin ! Thanks for opening this issue, and sorry about the delayed response. This is a cool use case! Makes sense to me overall to save this information. I'd...

Hi @adrianoesch ! Thank you for opening this issue and apologies for the delay. Just curious, if this issue is still relevant - how would you utilise these values for...

Thanks for the explanation @adrianoesch I have a couple of follow-up questions: 1. What do you think about including the **expected range** as a part of the description? I'm just...

Hi @adrianoesch , Got it, thanks for the explanation. I don't have any particular objection to adding this information to the description, so feel free to open a PR if...

Hmm I think I like the second option, though maybe I'd do this only for the training period: ``` The last {metric_name} value is {metric_value}. The average of the training...

Hi @asyarif93 ! Thanks for opening this issue and sorry for the delayed response. I believe that actually a custom SQL should work for the timestamp column today (in the...

Hi @bdstout , Thanks for opening this issue and apologies for the late reply! This makes a lot of sense, however due to a significant backlog I don't believe the...

Hi @christopherekfeldt ! Today we don't support showing all exposures under "exposures", however, you can set the `platform` meta attribute and exposures will be nested under it: ``` meta: platform:...

Actually @christopherekfeldt after discussing with the team I realized that it's actually a bug. The default should be `exposures`. Will update here when we have a fix for it.