Data Output Service
One transaction of Data Output is counted for each register read from a device's data storage. Learn more in Getting Data.
You need to define the Data Output limit per month for each Profile where your applications are running.
Example calculation
If a device reads one variable and the response contains 100 registers every 10 minutes (100 temperature data points), the operations will be:
- 100 registers × 6 reads per hour = 600 transactions per hour
- 600 transactions per hour × 720 hours per month = 432,000 transactions per month
Limits and behavior
If the limit is exceeded, any attempt to read data (GET) will be denied for the rest of the month.
Accessing data from dashboards, including downloading a .csv file from widgets, does not count toward the general Data Output limit. Instead, dashboards consume a separate Data Output limit specifically for dashboards. For more details, see Data Output for Dashboards.
The system will also count Data Output when using the function "Export Data" from the Device.
TagoSQL queries
TagoSQL executions are metered against this same Data Output allocation:
- Every execution that reaches the database (a cache miss, or a run with
"test": true) records the rows it returns as output usage, and is blocked once the monthly allocation is exhausted. - Results served from a query's cache are free and consume no output. See Caching.
- A query that fails the plan row cap still counts the rows the database consumed, so fix the query rather than retrying it.
Request limits are applied to interactions within the platform, including activities such as reading and exporting data. Read more about our Rate Limits.