Feedback
Feedback

If you are having issues with the exercises, please create a ticket on DevZone: devzone.nordicsemi.com
Drag & Drop Files, Choose Files to Upload You can upload up to 2 files.

How your device data flows into nRF Cloud

To use the platform well, it helps to picture the journey your data takes, from a single device at the edge all the way to a fleet-wide chart. This topic gives you that map at a high level. Lesson 2 takes a closer look at how a device connects and how these pieces are configured.

From a device to a project

In an nRF Connect SDK-based project, there is support for uploading data to nRF Cloud via HTTP and CoAP for Nordic cellular and Wi-Fi devices (nRF91, nRF92, nRF93, nRF7002, nRF7120) and Bluetooth LE devices (nRF52, nRF53, nRF54). Devices periodically check in with nRF Cloud, uploading small packets of data. Because embedded devices are often constrained by bandwidth and battery life, that data is sent in chunks and reassembled in the cloud. Every upload carries two things that tell nRF Cloud what it is and where it belongs: an identifier for the device, and a key that routes the data to the correct project.

A project is the warehouse for all the data related to one class of device, typically one hardware product. All the devices that check into a project together make up its fleet.

More on this

We’ll unpack device identifiers and project keys, and exactly how a device routes its data, in Lesson 2.

From projects to an organization

Projects live inside an organization, which usually maps to your company. One organization can contain many projects, for example one per product line. This gives you a simple hierarchy to keep in mind: an organization contains projects, and each project contains a fleet of devices. Lesson 2 goes deeper into this hierarchy and the finer-grained ways to group devices within a project.

Organization, project, and device hierarchy in nRF Cloud

An Organization is created when a new account is provisioned on nRF Cloud. You can then manage individual user access and Project setup. Note that free accounts can only provision a single Project. Please contact nRF Cloud support if you need more Projects.

How raw data becomes issues

When devices upload diagnostic data, nRF Cloud analyzes it and converts any detected problems into traces. A trace is a single occurrence of a problem, such as one crash. Rather than making you sift through thousands of near-identical crashes, the platform computes a signature for each trace and groups traces with matching signatures into an issue. An issue is one underlying problem; the traces inside it are its individual occurrences. You can always drill from an issue down into any specific trace.

Traces grouped into issues

How raw data becomes fleet-wide metrics

Devices collect metric readings on a regular schedule (such as an hourly or daily heartbeat), and report those readings down to nRF Cloud when connectivity is available. When readings are received by nRF Cloud, they are aggregated across the fleet. A value that starts life on one device becomes a data point in a fleet-wide chart, where you can slice and compare it by group or software version. The same pipeline powers device search and threshold alerts.

So the two things you care about most, “what’s broken?” and “how is the fleet doing?”, are both aggregations: many traces roll up into issues, and many readings roll up into fleet metrics.

Aggregated battery life comparison between two production batches

Switch language?

Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.

Your current progress is saved, and you can switch back anytime.

Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.