I'm trying to use the new Reporting feature in combination with Watcher on Elastic Cloud.
I want to generate a report and e-mail it to a whitelisted e-mail address.
The report is being generated, which takes about 2 minutes.
Sending the report through e-mail generates an error:
watch_id:daily_report state:executed trigger_event.type:schedule trigger_event.triggered_time:September 12th 2016, 10:01:33.865 trigger_event.schedule.scheduled_time:September 12th 2016, 10:01:33.864 messages: result.execution_time:September 12th 2016, 10:01:33.865 result.execution_duration:120,770 result.input.type:none result.input.status:success result.condition.type:always result.condition.status:success result.condition.met:true result.actions:{ "id": "email_admin", "type": "email", "status": "failure", "reason": "Unable to get attachment of type [http] with id [Verkopen 2016.pdf] in watch [daily_report] aborting watch execution" } _id:daily_report_1-2016-09-12T08:01:33.865Z _type:watch_record _index:.watch_history-2016.09.12 _score:1
Did some additional testing and it seems to be a performance issue.
With a 5 min interval, sometimes it sends an e-mail, sometimes it doesn't.
Is there a setting in Watcher so I can delay the e-mail sending until the report generation is finished?
using the log-view you can check out the log files and there you should find a reason, why the watch could not be executed. A couple of possible reasons
An empty response body was returned, nothing to attach
The HTTP response status did no start with a 2, so some error was likely returned
An exception occured when the content was downloaded
I will add some more information into that history message, so you dont need to take a look into the logs in the future.
Thanks for your reply.
I can find the timeout parm for webhooks, but I can't find a parm for setting e-mail action timeouts.
Do you know an alternative?
So, when you call a http attachment like this, inside of the attachment you just specify a request object, and this object can take the same parameters than the webhook, because we are using the same code internally. I hope this makes it more clear.
Thanks for clarification.
Unfortunately it doesn't solve the problem.
I've put both timeouts to 300s but I don't always receive an e-mail.
Generating the report takes about 2 mins.
Only solution seems to be to reduce the number of visualisations on the report.
thats better than nothing as it shows that there is a 502 (bad gateway) status code returned by kibana or a proxy inbetween. I would like to get the Elastic Cloud team involved into this. Would you mind sending me some data via email (like the watch you setup and your email address you are using for cloud), so I can forward this to the cloud team.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.