Live monitor and event history
Live monitor shows every door event as it happens, and the full access log of the tenant. Every role can use it.
Live
The Live tab starts with the latest events and adds new ones at the top as they arrive, highlighted. It shows up to 100 events.
- Pause freezes the list while you read (the indicator shows Paused); Resume catches up.
- Waiting for events… means nothing matches yet.
History
The History tab is the access log, newest first, 100 events at a time; Load more fetches older ones. The History button on the Doors page and View all on a cardholder's page open it filtered to that door or person.
Filters
Both tabs share two filters:
| Filter | Choices |
|---|---|
| Door | All doors, or one door. |
| Events | All events; Access decisions (granted, denied, unknown card); Denied and unknown cards; Door alarms (forced, held open, tamper); Controller events (online, offline, configuration applied). |
Each event shows its type, the reason of a denial, the door and the direction (in or out), the cardholder (a link to them) or Unknown, the card number (for Wiegand 26 cards the 10-digit number printed on the card, with facility code:card number beside it), who opened a door remotely (by …), details, and the time.
Through the API the log can also be filtered by time range, controller, cardholder and any set of event types (Edge API).
Event types
| Event | Type | When |
|---|---|---|
| Access granted | access_granted | A card was allowed through a door; the lock was released for the door's unlock time. |
| Access denied | access_denied | A known card was refused; see the reason below. |
| Unknown card | unknown_card | The card is not on the controller: not registered, in the pool, blocked or lost, its cardholder suspended or outside their validity period, or without access to any door of that controller. |
| Opened remotely | door_opened_remote | Someone opened the door from Edge (Doors and remote opening). |
| Door forced open | door_forced | The door opened without a granted access or a remote opening. |
| Door held open | door_held_open | The door stayed open longer than its held-open time. |
| Door closed | door_closed | The door closed again. |
| Controller online | controller_online | The controller answers its connector again. |
| Controller offline | controller_offline | The controller stopped answering its connector (the details say why, when known). |
| Configuration applied | config_applied | The controller applied a new configuration (the details give the version and the numbers of cards and schedules). |
| Tamper alarm | tamper | The controller's tamper switch was triggered. |
Door alarms and tamper events come from the controller's driver. The simulator reports granted, denied, unknown, remote openings, forced doors and configuration changes (Trying Edge with the simulator).
Denial reasons
| Reason | Code | Meaning |
|---|---|---|
| no access to this door | no_access | None of the cardholder's access groups has this door. |
| outside the schedule | outside_schedule | The groups have the door, but no window of their schedules is open now. |
| holiday | holiday | Today is a holiday and no holiday window is open. |
How the controller decides: Access groups → Who may pass.
How events arrive
- The controller records the event and keeps it in its own memory (a TrackBase002 holds 32,000 events).
- The connector reads each controller about once a second and writes the events to a queue on its disk, numbered in order.
- It uploads the queue in chunks. Edge stores each event exactly once and confirms; only then does the connector drop it. Events survive connector restarts and Internet outages and are never duplicated.
- New events reach every open Live monitor within a second or two.
When the connector or the Internet is down, events arrive late but complete, with the time the controller recorded them. A controller clock more than a day ahead or more than a year behind is not trusted: such events are stored at the time they arrived, and the details note the controller's time.
Controller online and offline events are recorded by Edge itself from the connector's reports.
Retention
The access log is kept for the server's event retention, 365 days by default, per whole month (Running Entrosity Edge).