Raw data

Raw data is an operational view for platform administrators. It contains sensitive network payloads and is not part of normal customer use. The global route shows all tenants or only unassigned messages. The tenant-owned route is fixed to that tenant and therefore has no misleading all-tenants filter.

Choose a time range, then filter by processing status, tenant assignment, DevEUI, or exact Netmore customer value. The summary counts describe only the messages currently loaded across the investigation. The first request fixes an upper time anchor. Select Load older entries to append 25 metadata records; Refresh clears the loaded records and starts again from a new anchor. A failed continuation leaves current evidence visible and can be retried.

Common status values are:

• Stored: the message was written successfully.
• Unknown device: no registered device matched the DevEUI.
• Malformed: the message could not be parsed completely.
• Duplicate: the platform recognized an already received message.

Flow execution has its own execution status and error records. A flow failure does not rewrite the raw message’s processing status.

The list initially loads metadata only. Select a message to open its immutable detail page and retrieve the exact MQTT body, sensor payload, topic, Netmore metadata, identifiers, and parsing details. The address includes receivedAt because the timestamp belongs to the TimescaleDB key. Copy raw payloads only into approved diagnostic channels; they can contain customer operational data.

For an assigned message, an authorized platform administrator can choose Request replay. Confirming queues the unchanged Raw message against the currently active Flow; it does not offer a historical Flow-version picker. The page displays execution ID, mode, and status. Choose Refresh status to read the latest state. Unassigned messages explain why replay is unavailable.