Forum Discussion
Monitoring by system center - deployed instances - how to relate the error to the item specified
Our infrastructure department uses system center to monitor our powerbi report server. One of the notification categories is "All deployment instances are discovered". This category checks whether the reports are runnable given the datasource credentials entered on the report server.
Within the notificatons returned it is not easily traceable which report has the culprit so we have to start a search manually by investigating each report manually. We receive a guid like ID from system center which should relate to the affected item like
7EB2A3ED-9DC4-42C5-9AE8-0D754AE909C6:KLFC005399\PBIRS
But the guid (7EB2A3ED-9DC4-42C5-9AE8-0D754AE909C6) itself does not lead to any item when we let a procedure check the total database with this guid
The datasource table within report server is encrypted, this could have been a good source to investigate but as being descripted it is not usable.
I was wondering how you solve these errors easily
2 Replies
- AnonymousNot applicable
Hi Anonymous ,
A way to find errors is to enable tracing in Power BI Desktop. You can then collect diagnostic information and review the information provided in the dialog. If you need to find error and crash logs of Power BI Desktop, you can find them by clicking “Open traces folder” in the logs section.
Power BI Desktop diagnostics collection - Power BI | Microsoft Learn
Or you can try to use fiddler. Fiddler is a free tool from Telerik that monitors HTTP traffic. You can see the traffic with the Power BI APIs from the client machine. This tool might show errors and other related information.
Troubleshoot Power BI embedded analytics application - Power BI | Microsoft Learn
If I have misunderstood your meaning, please provide more details.
Best Regards
Community Support Team _ RongtieIf this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- AnonymousNot applicable
Thank you Anonymous but i meant something else. It is about how to easily find inappropriate datasources on the database level, for instance outdated servernames. But these datasources are encrypted.