Azure Time Series Insights Gen2 API limits
This article describes the throughput, request, and concurrency limitations of the Time Series model and query APIs.
Model API - limits
The following limits are applied during query execution to fairly utilize resources among multiple environments and users:
| Applicable APIs | Limit name | Limit value | SKUs affected |
|---|---|---|---|
| All | Max number of TSM objects per request | 10,000 or 8 MB | Gen2 |
| All | Max model request execution time | 30 seconds | Gen2 |
| All | Max number of instances per environment | 1,000,000 | Gen2 |
| All | Max number of instance fields per instance | 100 | Gen2 |
| All | Max number of types per environment | 1,000 | Gen2 |
| All | Max number of variables per type | 100 | Gen2 |
| All | Max number of hierarchies per environment | 32 | Gen2 |
| All | Max number of hierarchies associated with an instance | 32 | Gen2 |
| All | Max hierarchy depth | 32 | Gen2 |
| All | Max number of characters in type name, hierarchy name, instance fields name, Time Series ID property value, Time Series ID each property name, Time Series name | 1,024 | Gen2 |
| All | Max size per instance | 16 KB | Gen2 |
Query APIs - limits
The following limits are applied during query execution to evenly utilize resources among environments and users:
| Applicable APIs | Limit name | Limit value | SKUs affected |
|---|---|---|---|
| Get Availability, Get EventSchema, Get Events, Get Series, Aggregate Series | Max number of concurrent requests per environment for Warm Store | 30 | Gen2 |
| Get Availability, Get EventSchema, Get Events, Get Series, Aggregate Series | Max number of concurrent requests per environment for Cold Store | 20 | Gen2 |
| Get Events, Get Series, Aggregate Series | Max response size | 16 MB | Gen2 |
| Get Events, Get Series, Aggregate Series | Max number of projected properties or variables | 50 | Gen2 |
| Aggregate Series | Max number of intervals in the response | 200,000 | Gen2 |
See also
For more information about application registration and the Azure Active Directory programming model, see Azure Active Directory for developers.
To learn about request and authentication parameters, read Authentication and authorization.
Tools that assist with testing HTTP requests and responses include:
Fiddler. This free web debugging proxy can intercept your REST requests, so you can diagnose the HTTP request and response messages.
JWT.io. You can use this tool to quickly dump the claims in your bearer token and then validate their contents.
Postman. This is a free HTTP request and response testing tool for debugging REST APIs.
Learn more about Azure Time Series Insights Gen2 by reviewing the Gen2 documentation.