Memfault's Android SDK hits v3.0!​

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.

Logging Improvements​

• Power up your log searching capabilities with filtering by log level, tags, regular expressions. This helps you find offending log lines faster than ever. Works for both Android and Real-Time products.

General Improvements​

• It is now possible to give Issues a new title with the UI.

Memfault Firmware Update CDN​

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.

Custom Metric Dashboards​

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.

General Improvements​

• You can now set the Device nickname and notes in the UI

• Allow force-refreshing the metric dashboards
• Issue filtering has been improved dramatically

Support for Complex Upgrade Paths​

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.

Reboot Reason Tracking​

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.

General​

Dashboards!​

The default landing page is now a Project Dashboard! Here, you'll find information such as:

• Top and Newest Issues
• Number of Traces, Bug Reports, and new Issues recently received
• The Software Version distribution
• Count of active Devices
• Number of Devices seen each day

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

Embedded​

• Add support for showing logs in the Issue detail view if the device is compiled and uses the Memfault Logging SDK.

• Add support for deleting a symbol file for a Software Version from the UI
• Show Device reboots in the Device detail view
• Improve Trace de-duplication when a Device crashes from within an ISR

Issue Reason Filter Multi-Select​

You can now filter by multiple Issue reasons at once. The filtering will persist in the browser's localStorage and will propagate to the URL so that you can send links to your co-workers of your favorite queries.

Device Metrics Zoom and Normalize​

We have added a zoom feature for the Device Metrics, as well as the ability to normalize the Y-axis units. This is useful for digging into a particular moment in time and comparing similar metrics.