We have been making a number of usability improvements to the Device Details
page including streamlining the amount of information visible when first viewing
the page. Below is the view when first viewing the Device details page,
highlighting software version and last seen.
Expanding this section now reveals more details on the status, config state and
Release information.
This is the first in a series of planned improvements to the Device Details page
designed to make it easier, and faster to get to the information that really
matters. These changes should also make the Device Details more usable for team
members who may be less familiar with Memfault, or do not require the level of
information available in the Device timeline.
The recently added Trace and Issue summary charts now also support drilldown and
we have added more details to the tooltips available on hover when viewing these
charts in your dashboards.
This combination of improvements should make it easier to analyze Issue data at
a glance and investigate when you spot something unexpected. You can read more
about the new
issue summary charts in our docs.
We have introduced two new Issue Charts for looking at Trace or Issue count
distributions between different populations of devices. These Charts allow
grouping by Issue ID or Issue Reason and support comparisons of different data
sets with Dashboard filters.
Cohorts can now be configured to require an additional Team member with the
right permissions to approve a Release Activation before it will be executed.
This adds an extra layer of assurance and security to the Device update process.
To activate this approval process, open the Cohort you want to enable it for,
open the Settings tab, and select a Team that can approve Release Activations.
Admins can create a new team under
Admin → Teams. When
activating a Release for this Cohort, a Release Activation Request will be
created requiring approval from one of the selected team members before
activation. Read more about this in
the OTA documentation.
Metrics can now be assigned a customizable tag. Adding tags allows for better
categorization of metrics and an improved search experience.
To try this feature, head to
Project Settings → Metrics
and select a Metric. In the Edit Metric modal window you can select or add new
tags. For example, you could tag all metrics related to your battery performance
with the tag battery. Read more about this
the Metrics documentation.
You request, we deliver. Dark Mode is now available for all Memfault users.
Whether you prefer a darker interface for its sleek look or its practicality,
this feature is designed to enhance your Memfault experience.
Switch between Dark and Light mode, or use your System Settings under the
profile dropdown in the top right corner.
Get Notified When Devices In Your Fleet Go Offline
Our new Device Offline Alert
triggers notifications when a monitored Device hasn't communicated with the
Memfault platform for a specified time period. You can configure the alert to
send a message via email, to a Slack channel, or configure webhooks to use
wherever else you need to be alerted. Device Offline Alerts are assessed every 5
minutes and can be tailored with start and end delays to manage noise and avoid
premature alerts due to brief connectivity losses. Read
the docs for more details on how
to setup and
configure Device Offline Alerts in Memfault.
We extended our
Processing Log
retention period from 7 to 60 days. Memfault's Processing Log provides a
chronological view of events and data essential for diagnosing SDK integration
issues and tracking data uploads. You can filter on date range, Device serial,
software version, log type, and level to quickly locate relevant entries. You
can also access detailed metadata on a log, and focus on specific transactions,
aiding in a streamlined diagnostic investigation. Read
the docs for more detail on how to best use the
Processing Log for troubleshooting Device behavior and SDK integrations in
Memfault.
We've introduced the ability to attach and manage Software Bill of Materials
(SBOMs) to software versions through Memfault. This new functionality will help
you streamline your software versioning process, keep track of everything that
goes into your version releases, and ensure that you can confidently meet
requirements associated with upcoming security regulations, like the EU Cyber
Resilience Act and US Cyber Trust Mark.
We support attaching a single SBOM file to a software version easily in the
Memfault web app by navigating to Versions tab > choose a Software Type that you
would like to attach your SBOM file to > click "Upload" under the SBOM column.
You can also download an existing SBOM from the same page.
We recommend uploading the SBOM via your CI build process for that specific
version and you can find more information about that in our
technical docs here, including how to integrate SBOMs
using our CLI.
We've introduced brand new filtering improvements within Memfault
Dashboards and Charts! These enhancements will help
you make better use of the data captured in Memfault and give you the ability to
manipulate your data to uncover deeper insights, identify trends, and highlight
relevant Metrics for your team.
Hardware version filtering: Dashboards can now also be filtered by
Hardware Version in combination with the Software Version and Cohort filters
Segment filtering (requires
Advanced Analytics Bundle):
Charts using the "by Population" rollup now also support the addition of
Metric conditions in combination with report type when creating segments
Let's say you want to see expected battery life data for sessions that had a
step count above 5000. Now you can add a condition that allows you to filter
the data based on that segment. For more information on segment filtering,
check out our
technical documentation here.
Create Issue Charts from Search: Create Issue/Trace Charts directly from
Issue search query to streamline reporting and root cause analysis.
Once you have selected all your filters on the Issues page, you can easily
create a Chart that already includes that filtering and add it to any
available Dashboards. For more information on segment filtering, check out our
technical documentation here.
We've introduced features to simplify the management of your platform usage with
Project Quotas and increase visibility of OTA related events and actions with an
Audit Log.
Quota Management: Our new
Quota management
system gives you more control and visibility over how your contracted Quotas are
utilized. With this new functionality, Organization admins can manage the
distribution of Quotas across Projects. Notifications will be triggered when a
usage level has been crossed and restrictions can be put in place when limits
are reached.
Audit Logs: The Audit Log is viewable by Organization admins and provides
visibility into all actions taken relating to the management and distribution of
OTA updates across your Project(s). As well as tracking actions, the Audit Log
also records the User performing each action and the time at which the action
was taken.
The Audit Log is currently only available to
customers on our Enterprise Plans and Users can find more information in our
technical documentation.
Product Analytics for Embedded Devices: Understand product usage, performance, and reliability like never before
We've introduced a brand new feature set within Memfault that helps you uncover
exactly how end-users interact with the devices you ship. Product Analytics
helps embedded teams and product owners understand product usage, performance,
and reliability like never before, giving them a clear view of feature and
function usage, adoption, and success rates.
With this new Product Analytics feature set comes the introduction of
Sessions. Sessions are a new
report type defined by the occurrence of an activity, allowing you to track
metrics in correlation with the usage of a specific feature or function on your
Device. It is up to the Memfault user to decide what they want to define as a
Session but when that Session is triggered, Memfault captures the length of that
Session and any important metrics you'd like to track specific to that activity.
This allows you to:
Track product engagement and adoption: Determine how newly launched
features are being used and adopted by your customers to refine and optimize
your product, driving higher satisfaction and retention.
Monitor and analyze feature usage patterns and behavior: Know when and how
your customers are using specific features to understand where you should be
focusing your efforts as you continue to develop your product.
Correlate feature usage with Device performance and reliability: Enhance
Memfault's existing functionality with the ability to answer really complex
questions about how your Devices are impacted by specific features.
Combining overall Device reliability data with product usage analytics will
unify embedded development teams, enabling them to make well-informed decisions
based on a comprehensive view of product health metrics.
We've introduced a new way to start collecting crash data and monitoring
firmware stability on your development devices in just minutes. With
Memfault Quickstart, firmware developers can
follow our simple, in-app guide to add Memfault to a real Device and start
reporting real Metric data related to connectivity, stability, and battery.
With Memfault Quickstart, you can experience key Memfault features with your
unique Device. After completing the guided integration, you can immediately:
Analyze a Coredump collected from your Device in our easy-to-use UI
Inspect activity happening on your Device on our Device Timeline
See what your data would look like in our charts and dashboards
Sessions on Device Timeline: Investigate Feature and Function Usage
Users can now view Sessions
– a new report type to capture Device activity – on their Device
Timeline. Sessions are reported when an associated feature or function is
active, and they will last as long as that feature or function is active.
Memfault users can define custom sessions using the Memfault SDK to track the
relevant activity on their devices and now have the ability to see when sessions
occurred and whether there are any Device reliability issues that align with
activity such as Traces, Coredumps collected, or unexpected Reboot Events.
Being able to track Sessions allows users to analyze specific metrics associated
with that session. For example, seeing how much your Device's battery drops
during a "workout" session on a wearable device or understanding how often a
credit card payment fails to process during a "checkout" session on a POS
Device. You can read more about all of our
Device Vitals functionality in
Memfault's technical documentation.
Learn more about capturing Metric Sessions for each SDK:
