Device Management

Devices are discovered automatically. PEEK tracks their presence, message rates, and state history.

Auto-Discovery

When a message arrives from a device ID that PEEK hasn't seen before, a new device record is created automatically. There is no registration step — devices appear as soon as they send their first message.

Device IDs are extracted differently depending on the source type:

  • MQTT: from the topic path (e.g., second segment of devices/sensor-001/telemetry)
  • Webhook: from the JSON payload fields (deviceId, device_id, etc.)

Device List

The Devices tab shows all discovered devices with filtering and sorting options:

  • Filter by status: All, Online, or Offline
  • Sort by: Last seen, message count, or name

Device Detail Page

Click on any device to open its detail page. Here you can see:

  • Hourly message chart — message volume over recent hours
  • State log — a timeline of online/offline transitions
  • Schema breakdown — which message types this device sends
  • Device-specific alerts — alerts scoped to this device

Friendly Names

By default, devices are identified by their raw device ID (e.g., a8:f7:32:01:bc:de). You can set a friendly name on any device to give it a human-readable label that appears throughout the dashboard.

Tip
PEEK also auto-populates friendly names from payload fields when available, so your devices may already have readable names.

Presence Tracking

PEEK monitors device presence by comparing each device's last seen timestamp against the source's offline threshold. When a device hasn't sent a message within the threshold window, it is marked as offline. When it sends a message again, it transitions back to online. Both transitions are logged in the device's state history.