Request entity too large when using custom endpoint in azure workbook

Ashwin Venkatesha 230 Reputation points
2024-05-17T20:13:29.9866667+00:00

I have a workbook that makes an api call and fetches results. These results are stored in a parameter and referenced/visualized by many widgets.

This happens to fail at scale (with 25k objects), I get a message

User's image

The query used here is,


print workload_response = '{GETWorkloadsAPI}'
| project parse_json(workload_response)
| mv-apply workload_response on (
		....this logic works at smaller scale....
    )

How to fix this issue? Any improvements that I can make to the query? And where can I find limits for how large data has to be?

Azure Monitor
Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
2,883 questions
0 comments No comments
{count} votes

Accepted answer
  1. Gowtham CP 2,215 Reputation points
    2024-05-18T13:24:02.9466667+00:00

    Hi Ashwin Venkatesha ,

    Thanks for reaching out to the Microsoft Q&A community.

    To address the "Request Entity Too Large" error in your Azure Workbook, you can optimize your API calls by filtering and aggregating data at the source to reduce the volume. Structure your queries to process data in smaller chunks and store raw data in external storage like Azure Data Explorer or Cosmos DB for further processing. Make sure you check and adhere to the size limits for Azure Workbooks and the custom endpoint. Additionally, consider using Azure Functions or third-party tools for preprocessing if necessary.

    If you found this solution useful, don't forget to upvote and accept it!

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful