Azure-docs: Cold storage of events

[fgheysels]

This part of this page explains that TSI PAYG keeps data in hot storage and in cold storage.
The data in cold storage is saved in a storage account using parquet files. Does this mean that the data is only available in parquet after the data has exceeded the 'hot storage ttl' ? Or is data immediately stored in cold storage ? (If that is the case, it means that we might consider to not create an 'archive endpoint/route' anymore on IoT Hub to archive the incoming data).

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e984b8e1-6bcb-cdbd-1cbc-cd7fafeb6b29
• Version Independent ID: 9612407a-f749-42c9-d2e0-331318427fe5
• Content: Data storage and ingress in Preview - Azure Time Series Insights
• Content Source: articles/time-series-insights/time-series-insights-update-storage-ingress.md
• Service: time-series-insights
• GitHub Login: @lyrana
• Microsoft Alias: lyhughes

[Mike-Ubezzi-MSFT]

@fgheysels Thank you for bringing this to our attention. It looks like you are seeking some clarification of the documentation. I will have the content team review this and make updates where appropriate.

[lyrana]

Hi @fgheysels great question. When data is ingested into TSI it is written to both warm and cold stores, and is available for query from either. Please note that to specify that you want to route a query to cold you'll set the storeType param and also note that there is a billing meter for cold.

[Mike-Ubezzi-MSFT]

@fgheysels I went ahead and changed this to a product-question and since it appears this has been answered, I am going to close this issue. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.