Skip to content
EbanEbanEban Docs

Device logs

Use Device Logs (Audit & Logs → Device Logs) to follow what each reader submits as it arrives, and how each submission was processed. To see when a device or relay agent went offline or came back, use Status Logs in Devices & agents.

What is logged

Section titled “What is logged”

Each row is one device submission:

  • Date: when the submission was received.
  • Device: the device label.
  • Source: how the reader recognised the person, such as fingerprint, facial, iris, or nfc for a contactless card.
  • Status: how the submission was processed.
    • success (green): successful_entry for a check-in, or successful_exit for a check-out.
    • failed (red): failed, which means nothing can be done about the submission.
    • warning (amber): every other state, all of which can still be resolved: processing, unknown_identification, unknown_schedule, backend_disabled, and resolved.
  • Message: the system’s explanation of the status.

Using the page

Section titled “Using the page”
  • Search the feed by device or message.
  • Pagination: the page and page size controls sit at the bottom.
  • Export the current view to Excel or PDF. The exported sheet carries more than the screen, adding the received time, the punch time, the device serial, and the attendee ID.
  • Refresh reloads the feed.

Live updates

Section titled “Live updates”

The page updates in real time as new device connectivity events arrive. Each event is automatically added to the top of the table, so you don’t need to Refresh to see the latest status changes.

What the page is for

Section titled “What the page is for”
  • Fleet health: see which readers are still sending scans, and which submissions are failing.
  • Employee disputes: confirm that a scan reached the system, and see why it did not become attendance.
  • Incident response: match a run of unmatched or failed submissions to attendance gaps.
Section titled “Related”