Memfault Retroactive Chunk/Symbol File Ingest

Question

If a heartbeat or other chunk reliant on symbol file data is ingested when there is no symbol file associated with the Software Version / buildID it seems like the chunk is totally lost. Is it possible to force re-evaluation of data once a matching Symbol File is uploaded? 
 
 The use case of this is in development when every iteration/flash of target hardware causes a new buildID and invalidates a base/released Software Version.

Syed Maysum Abbas Zaidi · Accepted Answer

Hi, 
 Yes Heartbeat/metric data that arrived before a matching symbol file was uploaded cannot be recovered. However, as soon as you upload the symbol file, all future heartbeat reports from that device will be decoded correctly going forward. 
 For your development workflow, since every firmware flash creates a new Build ID, the recommended approach is to script the symbol file upload as part of your build process using the Memfault CLI. This ensures the symbol file is always uploaded automatically right after each build, before the device starts sending data. 
 You can find instructions here: https://docs.memfault.com/docs/mcu/symbol-file-build-ids#uploading-symbol-file-with-build-id 
 Best Regards, Syed Maysum

Memfault Retroactive Chunk/Symbol File Ingest

Top Replies