Make your Issue list more organized and concise with the new Issue merging feature! Users can now merge Issues together by clicking the Merge button on the detail page of an Issue and then selecting which Issue to be its parent.
This workflow is especially useful when there are multiple Issues stemming from the same root cause, such as a stack overflow that presents itself with different backtraces.
This feature is available for both Android and Real-Time products.
Memfault's Bort SDK v3.0 has been released, which includes Memfault Caliper.
The Caliper system supports Trace collection from various subsystems, as well as per device and Fleet-wide metrics collection via the Android batterystats subsystem. Additional data sources, such as logs and system properties, are in development and are coming soon!
Memfault's Caliper is designed to have minimal effects on runtime performance, as well as consume less bandwidth and storage than sending bug reports.
To compare and contrast how Bug Reports and Memfault Caliper differ, please refer to the Bort SDK Reference docs page.
Memfault now supports serving firmware update payloads for Android devices using our Bort SDK. These payloads can be large, coming in between 1-3GB.
Because of this, serving these files out AWS S3 directly was too slow. So we now have support for serving these files through a global CDN!
In our tests, devices can see 50MB/s download speeds from the CDN, so your customers should experience quick firmware updates.
For more information, check out our Android OTA documentation.
Memfault captures Heartbeat metrics from devices. These metrics can then be viewed on a per-device basis. Customers have been asking for the ability to perform aggregates on these metrics over a Fleet of devices.
We are happy to say this feature is now available! Once a metric chart is created, you can aggregate over the devices within a Cohort or across a software version.
Many firmware projects have complex firmware upgrade paths. This might be to enable binary differential updates to save bandwidth or maybe to allow for a project to remove backwards-incompatible code.
For example, when upgrading a firmware from a 1.x to a 2.x release, the device might need to go through a migration firmware as shown below.
Memfault will now show an overview of why devices in your Fleet are rebooting. If a project implements the Reboot Reason Tracking module, Memfault will show this information in the main dashboard.
This functionality is coming soon for Android.
The default landing page is now a Project Dashboard! Here, you'll find information such as:
These dashboards are filterable by Cohort. This gives you the ability to filter the data to only internal or external devices, or to a particular customer.
Memfault Changelog for April
The changelog is now separated into 3 sections: Embedded, Android, and General.
