# Watcher Automated Email Reports

**URL:** <https://discuss.elastic.co/t/watcher-automated-email-reports/321586>\
**Category:** Kibana\
**Created:** [December 19, 2022, 6:35pm UTC](https://discuss.elastic.co/t/watcher-automated-email-reports/321586 "2022-12-19T18:35:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lmoore2210](https://avatars.discourse-cdn.com/v4/letter/l/f0a364/32.png) [@lmoore2210](https://discuss.elastic.co/u/lmoore2210)\
**Post date:** [December 19, 2022, 6:35pm UTC](https://discuss.elastic.co/t/watcher-automated-email-reports/321586/1 "2022-12-19T18:35:59Z")

</div>

Version 7.17:

I'm trying to set up a Watcher to send report emails following this guide:

> **[Automatically generate reports | Kibana Guide \[8.5\] | Elastic](https://www.elastic.co/guide/en/kibana/current/automating-report-generation.html)**
>
> Kibana provides you with several options to share \*Discover\* saved searches, dashboards, \*Visualize Library\* visualizations, and \*Canvas\* workpads with others, or on a website.

I set up the email account in the elasticsearch.yml with a pretty basic setup since our SMTP server does not require authentication. Something like this:

xpack.notification.email.account:  
mail1:  
host:  
port:

I'm running into this error:

1.) When I use the guide I'm getting a fail to parse for the reporting\_attachment during the simulation. Per the JSON I'm setting up, it doesn't seem like this reporting\_attachment is a valid setting. I can see the reporting section, but looks like a bug on the back end to me.

Is this a known issue or is there a work around?

---

<div class="post-metadata">

**Author:** ![drewdaemon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewdaemon/32/97779_2.png) [@drewdaemon](https://discuss.elastic.co/u/drewdaemon)\
**Post date:** [December 20, 2022, 5:43pm UTC](https://discuss.elastic.co/t/watcher-automated-email-reports/321586/2 "2022-12-20T17:43:23Z")

</div>

Hi @lmoore2210 — can you share the actual Elasticsearch DSL you're sending to the `_watcher/watch` address?

---

<div class="post-metadata">

**Author:** ![lmoore2210](https://avatars.discourse-cdn.com/v4/letter/l/f0a364/32.png) [@lmoore2210](https://discuss.elastic.co/u/lmoore2210)\
**Post date:** [December 20, 2022, 6:03pm UTC](https://discuss.elastic.co/t/watcher-automated-email-reports/321586/3 "2022-12-20T18:03:04Z")

</div>

So I need to clarify something, after posting this I was able to successfully send an email when the watcher fired. The issue is with simulating the watcher firing. So it's looking like a bug within the simulation not the actual watcher.

---

<div class="post-metadata">

**Author:** ![drewdaemon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewdaemon/32/97779_2.png) [@drewdaemon](https://discuss.elastic.co/u/drewdaemon)\
**Post date:** [December 20, 2022, 7:01pm UTC](https://discuss.elastic.co/t/watcher-automated-email-reports/321586/4 "2022-12-20T19:01:14Z")

</div>

Ah, okay then. Are you referring to the `_watcher/watch/<watch_id>/_execute` endpoint ([docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/watcher-api-execute-watch.html))?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 17, 2023, 7:01pm UTC](https://discuss.elastic.co/t/watcher-automated-email-reports/321586/5 "2023-01-17T19:01:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.