Kate on 11 Jun 2019 22:35:27
It would be helpful to be able to set up a distribution list of those to send refresh failure notifications to. Currently, only the owner receives an email, but we have several administrators that require notification when certain reports fail.
Administrator on 21 Jul 2021 16:58:18
Implemented
- Comments (51)
RE: Send Refresh Failure Notifications to Distribution List
This is great idea. If we can receive notification mail to system administrator group address, it would be better.
RE: Send Refresh Failure Notifications to Distribution List
Improved error messages needs to happen. I just get a message that says, file is corrupt. Which file?! There are hundreds!
RE: Send Refresh Failure Notifications to Distribution List
Power-BI came out 3.5 years ago and we are missing this one critical feature.
We are using Outlook rules from past 2 years, but this is not a best way as we have different DL for different reports.
For Example Dev vs Prod
We do not want to send the email notification for business users for the development reports.
RE: Send Refresh Failure Notifications to Distribution List
Fuck
RE: Send Refresh Failure Notifications to Distribution List
maybe you could define and use forwarding rules in MS Outlook for example (at least as a workaround)
RE: Send Refresh Failure Notifications to Distribution List
Necessary when you have a team maintaining PBI, which is the case at many medium/large companies.
RE: Send Refresh Failure Notifications to Distribution List
Should be able to specify a list of email addresses to notify through the On-Premises Gateway? That would be a great feature.
RE: Send Refresh Failure Notifications to Distribution List
Great idea
RE: Send Refresh Failure Notifications to Distribution List
Please add the name off Workspace into e-mail about Refresh failed. There is on Activity ID and Request ID and it would be really helpfull to know which workspace has trouble with refresh.
Thank you
RE: Send Refresh Failure Notifications to Distribution List
'Really the logging needs to include:
- Workspace name (or ID)
- Dataset name (or ID)
- Query name
- Error details
I just posted the following comment on:
https://powerbi.microsoft.com/en-us/blog/on-premises-data-gateway-november-update-is-now-available-2/
It is very hard to troubleshoot gateway refresh errors currently.
As far as I can tell (and the Microsoft support person who I raised a support call to), the gateway logs contain no information that you can use to find out which dataset in which workspace is a associated with a given failure.
This makes management of the Gateway very difficult. Power BI can retry refreshes multiple times, even when the refresh is destined to always fail (e.g. due to changes in the data source). This consumes a significant amount of resources in (1) data sources, (2) network, (3) gateway and (4) the Power BI Online service. So what appears as a mere annoyance, in a large organisation can have significant resource and capacity implications.
In a large organisation where many people and teams are using the same enterprise gateway, this can make the gateway very hard to manage (and the number of failing datasets can just increase over time).
Please Microsoft address this issue. At the moment you have what looks like a big design flaw in the logging mechanism that needs to be addressed.