File Address Template
During the exportation process, you will be able to customize the file address before exporting your data to TagoIO Files, and as a result, each chunk file will have its own file address. In the Advanced Settings, you can use key variables to change the path name that will be created inside your TagoIO Files. The variables you can use to customize your file address are listed below:
For example, the following file address template:
device/$DEVICE$/$FROM$_$TO$
Would result in a file address such as:
/device/6297aa7691e70a00654f9816/2022-04-01_2022-06-30.csv
Date variables such as $FROM$ and $TO$ will be in the ISO 8601 format (YYYY-MM-DD) When exporting a chunk to a location where a file already exists, all the data will be replaced with the new one.
Activating the Include Header option will enable headers on CSV-generated files. Headers will describe the variable's data in each column, just like a column's name, but you can disable them in the Advanced Settings to keep your files filled only with rows of data.
How exporting is billed
Notice that exporting data consumes the Data Output service.
The number of transactions billed is rounded to the next multiple of 10,000. For example:
- Exporting 700 registers will consume 10,000 data output transactions.
- Exporting 12,000 registers will consume 20,000 data output transactions.
- Exporting 32,000 registers will consume 40,000 data output transactions.
- Exporting 103,000 registers will consume 110,000 data output transactions.
The billing scheme mentioned above does not apply when fetching data using our
API. For example, when using a GET request, the amount of data consumed will be equal to the amount of data fetched.
Delete chunks
You can delete chunks to optimize your data storage. This is an irreversible process, and once done there is no going back, so make sure to be certain before removing anything. You can check the chunk range information by hovering your mouse over the graph before deleting the data.
You can keep track of all interactions made on this feature through the
Audit Log.