# Fetching a reporting dashboard that has been setup on Kibana as an email attachment using a Watch **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-alerting\ **Created:** [December 22, 2017, 4:24pm UTC](https://discuss.elastic.co/t/fetching-a-reporting-dashboard-that-has-been-setup-on-kibana-as-an-email-attachment-using-a-watch/113032 "2017-12-22T16:24:17Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Indiresh\_Ds](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/indiresh_ds/32/23382_2.png) [@Indiresh\_Ds](https://discuss.elastic.co/u/Indiresh_Ds)\ **Post date:** [December 22, 2017, 4:24pm UTC](https://discuss.elastic.co/t/fetching-a-reporting-dashboard-that-has-been-setup-on-kibana-as-an-email-attachment-using-a-watch/113032/1 "2017-12-22T16:24:17Z")
Hi there, I am trying to fetch the dashboard that is setup as an email attachment. I followed the instructions mentioned at [https://www.elastic.co/guide/en/kibana/current/automating-report-generation.html](https://www.elastic.co/guide/en/kibana/current/automating-report-generation.html) But somehow, it seems like the "email\_admin" tag does not work. Can this be done in any other way? Because I would really like to receive some very important dashboards as email alerts as it would eliminate the dependency of having to visit the portal every time I want to view the dashboard. Please find the below script that I have currently configured in order to achieve this. * * * ## { "trigger" : { "schedule": { "interval": "1h" } }, "actions" : { "email\_admin" : { "email": { "to": "abc@abc.com", "subject": "Error Monitoring Report", "attachments" : { "error\_report.pdf" : { "reporting" : { "url": "https://\", "retries":6, "interval":"1s", "auth":{ "basic":{ "username":"",//I tried entering my Kibana login credentials here. But clearly, I don't think that will work since "email\_admin" //probably refers to an admin user. And I am not an admin user. "password":"" } } } } } } } } } ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [December 29, 2017, 12:11pm UTC](https://discuss.elastic.co/t/fetching-a-reporting-dashboard-that-has-been-setup-on-kibana-as-an-email-attachment-using-a-watch/113032/2 "2017-12-29T12:11:19Z")
Hi, You need to configure the email address in elasticsearch.yml. Here are our docs: [https://www.elastic.co/guide/en/x-pack/6.1/actions-email.html#configuring-email](https://www.elastic.co/guide/en/x-pack/6.1/actions-email.html#configuring-email) [https://www.elastic.co/guide/en/x-pack/6.1/actions-email.html#configuring-email](https://www.elastic.co/guide/en/x-pack/6.1/actions-email.html#configuring-email) Let me know if this doesn't help? Thanks, Bhavya ---
**Author:** ![Indiresh\_Ds](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/indiresh_ds/32/23382_2.png) [@Indiresh\_Ds](https://discuss.elastic.co/u/Indiresh_Ds)\ **Post date:** [January 2, 2018, 5:51pm UTC](https://discuss.elastic.co/t/fetching-a-reporting-dashboard-that-has-been-setup-on-kibana-as-an-email-attachment-using-a-watch/113032/3 "2018-01-02T17:51:46Z")
Hello Bhavya, Thank you so much for your response. 🙂 My email address has been configured in elasticsearch.yml I have already configured several other watches that are successfully returning log payload info as email alerts. I was concerned about the role of the "email\_admin" tag. But it looks like it has nothing to do with access permissions, etc. Like I guessed, if my email address is configured in elasticsearch.yml, I should be able to receive reports through email. Thank you once again for confirming this point. 🙂 However, I would like to bring to your notice that I see an error saying **"sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target**" when I tried simulating the watch. I did not want to pose this question earlier because I really wasn't sure whether this was the only factor responsible for failure. But now I think I am pretty sure. 🙂 This obviously means that Kibana's self signed certificate is not being recognized by Watcher, right? And in order to resolve this and achieve generation of automated reports, I am supposed to ensure that justified certificate authorities are in place. Am I correct? I came to this conclusion after referring to the last couple of comments at [https://github.com/elastic/kibana/issues/9783](https://github.com/elastic/kibana/issues/9783) ---
**Author:** ![bhavyarm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bhavyarm/32/22392_2.png) [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)\ **Post date:** [January 2, 2018, 6:06pm UTC](https://discuss.elastic.co/t/fetching-a-reporting-dashboard-that-has-been-setup-on-kibana-as-an-email-attachment-using-a-watch/113032/4 "2018-01-02T18:06:21Z")
Yep :). That's correct. We have this blogpost [https://www.elastic.co/blog/tls-elastic-stack-elasticsearch-kibana-logstash-filebeat](https://www.elastic.co/blog/tls-elastic-stack-elasticsearch-kibana-logstash-filebeat) for reference if you need help. Thanks, Bhavya ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 30, 2018, 6:06pm UTC](https://discuss.elastic.co/t/fetching-a-reporting-dashboard-that-has-been-setup-on-kibana-as-an-email-attachment-using-a-watch/113032/5 "2018-01-30T18:06:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.