Data source error: DataSource.Error: <pii>Web.Contents failed to get contents from (long url here) 400): Bad Request. The exception was raised by the IDbCommand interface. Table: EventTelemetry.

bfranco95 commented 3 years ago

What project is affected?

We are building a chatbot and utilizing the Analytics template for Power BI.

What happens?

Attempting to open the Power BI dashboard which has worked previously.

We get the following error:

What are the steps to reproduce this issue?

Re-deploying the template produces the same exact issue.

What were you expecting to happen?

We have been able to see the dashboard before, but now we cannot even see anything and just run into this error.

bfranco95 commented 3 years ago

Checking for any updates here?

ryanisgrig commented 3 years ago

Hi @bfranco95,

I tested this afternoon on my end with a fresh install of the Virtual Assistant, new Azure resources and a new instance of the Power BI template. This works successfully for myself. I have a few questions to follow up:

What version of the VA template are you using? Did the Power BI error occur after updating it or did it just stop working one day?
Is telemetry still populating in the Application Insights resource as expected?
What version of Power BI desktop are you using? See: Help > About
Are you successfully authenticated to the App Insights data source? I am authenticated using my organizational account, you can verify under Home > Transform data > Data source settings > Edit permissions > Credentials: Edit

Tagging Support for backup!

tomSauret847 commented 3 years ago

I ran into tis same issue. What we found was the app insights data was to large to pull from app insights. We ended up exporting app insights data to a Blob storage and then rebuilding the report to query the data from Blob as a work around to this issue.

stevkan commented 3 years ago

@tomSauret847, can you explain how you determined that the app insights data was too large to pull?

tomSauret847 commented 3 years ago

@stevkan We opened a case with the App Insights support team and had their help in investigating this. After running a fiddler trace with the report refreshing it was uncovered that the data set was too large for the app insights API, that is what triggers the 400 error. It was larger than the 100 MB that the API allows. We have several bots using this reporting and when they become well used we change the reporting to pull from Blob storage instead of app insights. This requires exporting the data in the App insights workspace and reconfiguring the query to use the Blob storage connector.

bfranco95 commented 3 years ago

Here are the answers to your question @ryanlengel

• What version of the VA template are you using? Did the Power BI error occur after updating it or did it just stop working one day? o It just stopped working one day. No updates were made to the template. • Is telemetry still populating in the Application Insights resource as expected? o Yes • What version of Power BI desktop are you using? See: Help > About o Version: 2.96.1061.0 64-bit (August 2021)

• Are you successfully authenticated to the App Insights data source? I am authenticated using my organizational account, you can verify under Home > Transform data > Data source settings > Edit permissions > Credentials: Edit o I am using my organization account, which worked in the past.

stevkan commented 3 years ago

@bfranco95, have you investigated to see if you are running into the same issue that @tomSauret847 experienced (i.e. the response data is too large)? At the moment, this is looking to be the cause. And, it makes sense in that as data is collected but the size is low, it would work. When the size reaches the limit, it suddenly stops working.

Are you in a position where you can check / test this? Are you able to test against App Insights outside of Power BI to see if the result is the same?

stevkan commented 3 years ago

Closing as resolved. If the issue persists, please feel free to reopen.

lshade commented 2 years ago

@stevkan We should reopen this. I also have bots with multiple clients running in production that have exceeded the data limits after only a day or two. They are getting this same error. What's the recommended solution?

@tomSauret847 are you able to share the queries/scripts from your remediation?

tom600x commented 2 years ago

Please reopen @stevkan I also have a few customers who need this working without the workaround of dumping the data to SQL

lshade commented 2 years ago

Inquiring to see if someone can provide an updated version of the template configured to use blob storage instead of running the App Insights Query. We've set up a Diagnostic Setting on the LAW to archive the data in blob storage

microsoft / botframework-solutions