Automatically translate this page?

How to manage device storage and prevent your monthly bill from bloating?

Ways to limit the volume of data stored in devices and assigned devices.

Flespi devices collect, save, and store all messages with a particular ident (IMEI). If a tracker actively sends messages (e.g. every 5 seconds), the volume of stored messages in the device storage can grow rapidly. This can lead to the following consequences:

  • run out of space — even though device storage for a commercial account is limited to a substantial 10GB, you’d better keep an eye on it to avoid losing messages.

  • incur unnecessary expenses — each additional GB of stored data after the first GB will cost you an extra $1/month. It’s totally OK to store data in flespi for up to 10 years but if you were not planning that, you should take care of all the incoming messages in a timely manner.

Note: the same is true for devices assigned to calculators (aka assigned devices) — they can also hold up to 10GB of calculated intervals.

So, what you can do to use device storage efficiently and not overpay:

  • Messages TTL — adjust the value of this parameter in device configuration so that you don’t store the old data that you don’t need. The default value is 365 days. If set to 0, messages will not be saved.

  • Messages rotation size — the max size of stored messages in KB; you set it to a smaller value than the allowed device storage (10GB) to avoid accidental bloating. When reached, the device storage will be rotated (the oldest messages will be deleted freeing up space for the new ones).

    messages ttl and messages rotation size flespi device
  • Intervals TTL — same as messages_ttl but for intervals stored in assigned devices. Can be set up in a calculator configuration.
  • Intervals rotation size — same as Messages rotation size but for intervals stored in assigned devices. Can be set up in a calculator configuration. intervals ttl in flespi calculators

See also
Configure a stream to forward device messages from IoT or telematics hardware into the Google ecosystem.
Configuring the telemetry data forwarding from flespi to the Key Telematics tracking system.