Ingest History

The Ingest History shows the raw tag reads and telemetry arriving from every device in your fleet, exactly as readers sent them. This is the earliest point data reaches Tagnet: nothing here has been grouped into scan events, evaluated by movement rules, or acted on by a workflow yet. When you need to know what a reader actually saw, rather than what Tagnet concluded from it, this is the page to check.

Raw Data vs. Processed Data

Tagnet builds several layers of meaning on top of the raw ingest stream:

Layer	What it shows	Where to look
Raw ingest	Every individual tag read and telemetry report exactly as received	Ingest History (this page)
Scan events	Reads grouped into passages by cooldown, timing, and processing mode	Scan Events
Movement rules & workflows	Automated inventory movement and actions triggered by scan events	Movement Rules, Workflows

If a tag was read but never shows up as a scan event or an inventory movement, the Ingest History is where you confirm the raw read actually arrived, before you go looking for a configuration problem further down the pipeline. If reads look right here but nothing downstream reflects them, the issue is in scan processing or a rule, not the reader.

Note: The Live Reads tab also shows tag activity, but as a live, deduplicated, action-oriented view (map, move, decommission) rather than a historical, per-event record. See Live Reads vs Ingest History for the comparison.

Opening the Ingest History

From the Devices page, open the Ingest History tab. You can also navigate directly to /devices/ingest.

Note: Links to the old /device-events page redirect here automatically, and per-device links redirect to that device's Ingest data tab. See Devices for the per-device view and Inventory for a single item's tag history.

Permissions

Permission	What It Allows
View Devices	Access the Ingest History and view tag reads and telemetry

Search and Filters

Search

Type into the search box to match a tag EPC, an event type (for example DIRECTIONALITY or heartbeat), a telemetry message, or a device name. Results update automatically as you type.

Filter Drawer

Click the filter icon next to the search bar to open the filter drawer.

Filter	Description
Event Type	All events (default), Tag reads only, a single tag-read type such as DIRECTIONALITY or BEARING, All telemetry, or a single telemetry type such as heartbeat or error. Both type lists are whatever your devices have actually sent. The Type chip on each row names the kind of read or telemetry it is
Device	Show only reads and telemetry from a specific device
Time Range	Off by default. Last hour, Last 24 hours and Last 7 days set a start and leave the end open; or set From and To dates, each with an optional time (the start or end of that day when the time is blank)

Filter Chips

Active filters appear as chips below the search bar. A Time chip appears only when you set a range, so an unfiltered list really is unfiltered: nothing is hidden by a default window. Your search, event type, device, and time range are remembered for the rest of your session, so leaving to check a device's configuration and coming back does not lose them; Clear All forgets them. Click a chip's X to remove that filter, or Clear All to reset everything at once.

A Batch chip appears when you arrive from a "View batch reads" link (see Batch Correlation below); closing it clears the batch filter.

The Events Table

Tag reads and telemetry share one list, newest first, so a reader's heartbeat, its error, and the reads around them appear in the order they happened. The Type column tells the two apart, and the Event Type filter narrows to either kind. Rows read like log lines: four columns, with everything else one click away in the row's detail dialog.

Columns

Column	Description
Time	When the device reported the event
Device	Which device reported it
Type	The kind of read as the reader sent it (CUSTOM or SIMPLE from an FX reader, DIRECTIONALITY, DIRECTIONALITY_RAW or BEARING from an ATR7000, or Tag read when the reader gave no type), or the telemetry category: Heartbeat, Error, Warning, Status, and so on (color-coded)
Details	For a tag read: the tag's EPC (formatted per your tag ID display preference, with a copy button), the mapped inventory item and type linking to the item page or an Unmapped chip, and the RF facts in one line: antenna port, signal strength in dBm, and the read count when more than one read was folded into the event. For telemetry: the message (truncated, full text on hover) and, for heartbeats, CPU, RAM, temperature, and uptime

Loading Older Events

The newest 50 events matching your filters load first. Click Load older events at the bottom to append the next 50, as far back as the time range allows, or all the way back when no range is set; the list says when it has reached the end. Loading older events costs the same however far back you go, so scrolling through a busy reader's history stays quick. The page header's Refresh button starts over from the newest event.

RSSI Color Coding

The list shows signal strength as plain text; the tag read's detail dialog color-codes it:

RSSI Range	Color	Signal Quality
> -40 dBm	Green	Excellent
> -60 dBm	Blue	Good
> -75 dBm	Orange	Fair
≤ -75 dBm	Red	Weak

Latency Color Coding

Latency (the delay between the device's own timestamp and when Tagnet received the event) appears in the detail dialogs, color-coded:

Latency	Color	Meaning
Negative	Blue	Clock skew between the reader and the server
< 1 second	Green	Normal
< 5 seconds	Default	Acceptable
< 30 seconds	Amber	Delayed
≥ 30 seconds	Red	Significantly delayed

Tag Read Details

Click any tag read row to open its detail dialog:

• Tag Information: Tag ID (full value), mapped inventory item and type (or Unmapped), device, timestamp, received-at time, event type, and batch (with a View batch reads button)
• RF Data: Antenna port and name, RSSI, read count, channel (MHz), phase (degrees), format, event number
• Direction & Zone: Movement direction, state, and zone, if the reader provides them. For an ATR7000 directionality event this also shows when the tag was last seen and, on a timed-out event, how long after that the reader gave up on it
• Tag trail: On an ATR7000 timed-out event sent with Include location history or Include zone history on (see the ATR7000 directionality guide), an overhead map of the positions the reader computed for the tag, in feet from the reader with the reader's True-North up, colored from the first sample to the last. Zoom to tag fits the map to the positions and Reader range shows them against the reader's reach, worked out from its reader and tag heights. The reader itself is drawn to scale. Hover a position for its time, offset, coordinates, distance from the reader and the zone at that time, or use Play and the slider to replay the pass. The zone history draws as two timelines, the last 90 seconds before the report and the whole history the reader kept for the tag, with gaps of five minutes or more shown as not seen. The positions are also available as a table
• GPS Position: Where the reader was when it made the read, shown as coordinates. Select them to see the spot on a map. Appears only on reads from a GPS-equipped reader (an FXR90 with Include GPS position on) that had a fix. See GPS Position
• Bearing/Location: Azimuth and elevation with confidence levels, if supported
• Memory Banks: TID, PC, CRC, and User Memory values, if available
• Raw JSON: The complete event payload for diagnostic purposes. Shown only for reads stored while Store raw payload per read or a capture override was on in the TagRead retention policy; it is off by default.

Batch Correlation

Every ingest request a reader sends is stamped with a batch ID shared by all the reads in that payload. Click View batch reads in a tag read's detail dialog to jump to the Ingest History filtered to every read that arrived in that same batch, useful for confirming what a single reader payload actually contained, for example when several tags should have been read together at a dock door but only some of them show up downstream.

Telemetry Details

Click any telemetry row to view comprehensive device metrics, organized into sections that appear only when the event carries that data:

• Event Information: Device, event type, timestamps, vendor, component
• System Metrics: CPU and RAM usage, free RAM and flash storage, temperature, PA temperature, uptime, power source, NTP offset
• Radio & RFID: Radio status, activity, connection state, antennas connected, total tag reads
• Errors & Warnings: Error and warning counts, severity, and message
• Antennas: Per-antenna status and read counts, if reported
• GPIO State: GPI/GPO states, if available
• Raw JSON: The complete telemetry payload

Live Updates

While the page is open, new matching reads and telemetry light a New badge on the Refresh button in the page header instead of streaming directly into the table, since a high-volume reader would otherwise make the grid unreadable while you're trying to read it. Click Refresh to pull the new events in. Updates are throttled during bursts to keep the page responsive.

Live updates arrive over the same connection the page itself uses. If the browser loses its connection to the server, the standard reconnect overlay appears; once it returns, click Refresh to pick up anything that arrived in between.

Raw Capture and Retention

Raw tag reads and telemetry are governed by the Tag Read Retention and Telemetry Retention policies. If an administrator has turned off raw capture to save storage on a high-traffic deployment, a warning banner explains that new reads are not being stored, while scan processing and hourly rollups continue unaffected. The banner links to Policies, where an admin can turn capture back on or grant a temporary capture window for a support investigation.

Where Else You'll See This Data

• A single device's own reads: open the device's detail page and select the Ingest data tab. See Devices.
• A single item's tag history: open the inventory item's detail page and select the Ingest data tab. See Inventory.
• A specific tag, anywhere in the fleet: paste 4 or more hex characters of a tag ID into Global Search to jump straight here, filtered to that tag, whether or not it's mapped to an item.

Use Cases

• Diagnosing read issues: Check RSSI and latency values to understand why tags aren't being read reliably or why data is arriving late
• Verifying reader health: Review telemetry for CPU spikes, temperature warnings, or antenna disconnections
• Confirming the raw layer before blaming automation: If a scan event or inventory movement didn't happen the way you expected, check here first to see whether the read actually arrived
• Investigating tag behavior: Examine phase data and signal patterns for specific tags
• Batch correlation: Use "View batch reads" to see everything a single reader payload contained
• Finding an unmapped tag: Search for a tag ID here, or from Global Search, to see whether an unmapped tag has been scanned anywhere before you map it to an item