-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for emailing reports at regular intervals? #1231
Comments
Hi @jasonshah, we're currently discussing the addition of a feature like this internally. Specifically we'd like to support an api for fetching a static image of a given chart or dashboard, which could then easily extended to send out emails automatically. Will post back as soon as we've settled on a technical solution for the implementation and have a better idea of the timeline. cc @ascott |
Hi Williaster, but I couldn't able to add one more option for PDF export in the "js-explore-actions". |
do you have a PR, or can you provide more information about how you implemented the pdf export? we are thinking about using a headless browser to take screenshots of dashboards (so the result would be a .png) with a couple of size options. adding the ability to directly download a chart from the explore page would also be pretty cool and potentially useful. |
Seconded. I'm very interested in this feature being added. |
+1 |
I worked on integrating a headless browser to render chart images but never got around to finish the work: If someone want to take over this branch, wrap things up and submit a PR you're welcomed to do so. |
Definitely is a hotly requested feature from our userbase. |
@htruongaff then that's a good chance to contribute the work and make both the superset community and your userbase happy 👍 |
Any updates on this? @williaster |
@htruongaff , do we have any update on this post. we are also looking for the same feature. |
+1 |
Any update on this? We're looking for a similar kind of feature, and would be keen to collaborate on its creation. |
@corvilpm looking forward to your pr 👍 |
Is there an existing fork or branch where this project has been started? |
+1 |
1 similar comment
+1 |
+1 for regular PDF email support |
Hello. We also need this feature badly. |
+1 |
I have a PR for this feature - #5294
Use Firefox / Chrome headless browsers. It also works with phantomjs, if needed. |
+1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue |
We are using superset with schedule report emailing, it works great for us. In the below article, we have published steps to make deployment easy for superset with schedule report emailing. |
@nabhosal I tried your method. However I'm getting an error on docker logs when trying to schedule email reports. The message looks like this selenium.common.exceptions.SessionNotCreatedException: Message: Unable to find a matching set of capabilities What version of Firefox you've installed? Have you installed anything else other than the ones which came with docker? |
Hi,
I started exploring Caravel this past week, and I'm loving it. I am exploring working with my engineering team to roll it out as an enhancement/replacement to our internally-built reporting solution.
Are there any plans to support emailing a Dashboard nightly/weekly to users as PDF? While the solution is obviously more powerful when you interact with it on the web, there are a number of users who could benefit from what Dashboards offer if they could see an email with a snapshot of the Dashboard in-line or as an attached PDF. A user would be able to request a Dashboard to be emailed to them nightly or weekly on a specified date, and the admin would be able to configure the email server through which the Dashboard is sent.
This would allow us to centralize towards use of Caravel as a platform for more use cases, vs. implementing/retaining another solution that is specifically suited to this purpose.
(I would have posted this to the Google Group, but my membership is still pending.)
The text was updated successfully, but these errors were encountered: