## Through the Bort SDK​

When configured with a Memfault Project Key, the Bort SDK will automatically start uploading device diagnostics information into Memfault.

During development, it makes sense to configure the Bort SDK to send data at a higher frequency. You can do this by enabling development mode

## Using the Memfault CLI​

info

This guide assumes the Memfault CLI tool installed. If it is not installed it yet, please follow the installation instructions.

There are a few ways to upload data with the CLI. The following examples will use an Organization Auth Token. Please refer to the Memfault CLI Authentication section for more information about the different forms of authentication.

A Memfault Archive File (MAR) is an archive format that is generated by the Bort SDK containing many files in a compressed ZIP archive. The rationale behind creating and using a bundle containing many files is:

• To minimize data bandwidth and HTTP requests for cellular devices and minimize CPU and power consumption for battery-operated devices.
• To make it easier for customers to send large amounts of device-generated data to Memfault.
• To be able to send Memfault-specific data alongside the raw files that the operating system creates, such as Android Tombstone files.
• To be able to associate data within a MAR file to multiple devices. This enables our Android Multi-Device support.

To upload a MAR file that is located at, for example /path/to/device-data.mar, run the appropriate command:

note

The Software Type, Software Version, Hardware Version, and Device Serial parameters of the CLI command below should match that of the device which generated the MAR file.