Nordic Semiconductor's nRF Connect SDK now has Memfault's SDK built-in, allowing for customers and users of Nordic's chips and tools to integrate and use Memfault in minutes.
Check out our press release for more information!
As for new Memfault features, we made improvements to symbol-file uploading and downloading, added favorite projects, and sped everything up a bit.
One of Memfault's most capable features is Metrics. With Metrics, you can determine how specific metrics on a single device correlate with each other to root cause performance and power regressions, or aggregate them on a fleet level and determine whether the health of your fleet of devices is improving over time!
We're announcing new features today which should help make our metrics feature more usable.
First, users can now view all the Metric names that have been received from heartbeat events in the Settings → Metrics page. This allows for easy auditing of metric names and configurations.
If you find any that are stale or shouldn't be tracked anymore, you can archive them.
When Edit is clicked, users can configure the valid ranges for the metric, which will improve the displayed charts by normalizing the Y-axis to possible values. An example of where this could be useful is battery life, where the min and max values are 0-100.
Users can also specify a single value for Memfault to ignore, such as
0xffffffff, which can represent the absence of a value.
These new features will enable developers and customer support representatives to more easily dig into the health of a single device and the entire fleet.
That's not all though! We've made more improvements to symbol file uploading, bugreport filtering, and the archiving of software versions.
The day you have all (maybe) been waiting for is here! Anyone can now sign up for a free trial of Memfault! There is no sales team in your way of getting your devices integrated with Memfault and monitoring your fleet of devices.
Check out our press release to learn more.
You can now view, invite, remove, and set roles for all users in your Organization!
You can find this setting under Admin → Users. This feature is only available for admins of an Organization.
Many improvements have been happening on the Android side of the product, primarily when viewing Caliper data within the Timeline view. We now include almost every type of data a device can send in the timeline view, such as drop box manager entries, log files, traces, and more.
View the timeline by day, drill into specific hours, and navigate to the pieces of data that you want to investigate!
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.
