Timeseries Insights API pricing
This document explains Timeseries Insights API pricing details. The pricing is the same for all regions where we provide the service.
Timeseries Insights is charged based on the amount of data ingested into the system. The data size is measured based on the ingested JSON byte size from the field DataSet.dataSources for the create API. If the inputs are not json-line files in Cloud Storage, such as BigQuery or online update from appendEvents, a best effort estimate is used as if the input is JSON. Note the data size is the uncompressed size, although the dataSources URI accepts commonly compressed files.
Timeseries Insights does not charge individual APIs separately, especially the evaluateSlice and query APIs. They are rate limited based on the amount of data in the system at 20K/day evaluateSlice/query requests per GB data. The appendEvents requests are limited to 1% increment of data size per day.
| Commitment Model | Cost | Details |
|---|---|---|
| Pay as you go | $16/GB/month | Billed monthly while the dataset is active. The data size is assessed daily. |
Pricing examples:
Example 1: Customer StaticHistory uses Timeseries Insights to explore historical data. They ingested 10G JSON data stored in Cloud
Storage, and sent queries with detection time falling in the time range of the historical data. For each month, the customer is
charged $16*10 = $160.
Example 2: Customer ActiveFeed uses Timeseries Insights to catch changes at real time. They started with 100G history data at the
beginning of the month, and their data feed adds 1G data each day. At the end of a 30-day month, the customer is charged
$16*(100 + 101 + ... + 129)/30 = $16*114.5 = $1832.
(Non)-Example 3: Customer ZeroStart wants to start without any history and accumulates data as it goes. Although the system does not strictly disallow appendEvents, this is strongly discouraged, as the evaluateSlice and query APIs only function with a sufficient history.