• State Verified Answer
  • Replies 3 replies
  • Subscribers 87 subscribers
  • Views 209 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 358305
Options

Memfault Retroactive Chunk/Symbol File Ingest

musclemadness

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.

Parents
  • 0

    Note also that unlike heartbeat data, coredumps will be automatically reprocessed if a matching symbol file is uploaded later. Syed Maysum's suggestion about using the Memfault CLI to facilitate symbol file upload is excellent- before flashing a build you want to send Memfault data from, you can run a command like this:

    ❯ memfault --org-token $MEMFAULT_ORG_TOKEN --org $MEMFAULT_ORG --project $MEMFAULT_PROJECT upload-mcu-symbols build/zephyr/zephyr.elf

    See the link provided for more reference information, including how to generate the MEMFAULT_ORG_TOKEN.

    Thanks!
    Noah

Reply
  • 0

    Note also that unlike heartbeat data, coredumps will be automatically reprocessed if a matching symbol file is uploaded later. Syed Maysum's suggestion about using the Memfault CLI to facilitate symbol file upload is excellent- before flashing a build you want to send Memfault data from, you can run a command like this:

    ❯ memfault --org-token $MEMFAULT_ORG_TOKEN --org $MEMFAULT_ORG --project $MEMFAULT_PROJECT upload-mcu-symbols build/zephyr/zephyr.elf

    See the link provided for more reference information, including how to generate the MEMFAULT_ORG_TOKEN.

    Thanks!
    Noah

Children
No Data
Related
Terms of service