Hi Everyone! We are using column_anomaly detectio...
# community-support
o
Hi Everyone! We are using column_anomaly detection tests for some of our models and would like to link the errors to a dashboard in the description. Is there a way currently to add a URL to the description? Thanks in advance!
e
Hi Oliver, do you mean you want the test description to contain the URL to a BI dashboard that depends on that column?
o
hi @Ella Katz! Yes. This is my goal. like an additional parameter for URL ( similar to an Exposure )
e
that's an interesting suggestion! Would be great if you can open a github issue for that 🙂 In the meantime, I can suggest adding the url in the test description under:
Copy code
tests:
          - unique:
              config:
                severity: error
              meta:
                description: The column impacts the dashboard in this url: <url>
btw, wouldn't it make more sense to add the url of the dashboard to the description of the column rather than the description of the column test?
o
I can suggest adding the url in the test description under:
we are currently doing this but it looks very ugly having an actual URL there. We tried shortening it but it just looks odd.
btw, wouldn’t it make more sense to add the url of the dashboard to the description of the column rather than the description of the column test?
Ideally the final outcome would be a link in the alert itself that redirects to the URL. The description is a string text that we don’t know how to format - if at all - and how scalable it is formatting each description?
e
I understand. So ideally what you want here is to have a list of impacted dashboards in your alerts?
o
we could say that, yes!
e
So that’s definitely in our roadmap, but we plan to base it on the dbt exposures. Do you use those?
o
“Jain” a german would say. it’s a mix of yes and now. we created exposures once but kinda abandoned them because they seemed to be rather useless, especially when we use Elementary’s lineage graph instead of the dbt default one.
how do you imagine delivering it with Exposures?
o
Hey @Oliver Szotyori, you can also use Slack Markdown syntax in your description, so you can do:
Copy code
tests:
          - unique:
              config:
                severity: error
              meta:
                description: The column impacts this <<http://my/dashboard/%7Cdashboard>>