Skip to content

Activity: alerts, commands and visits ​

Three Telemetry Logs screens record what happened to your coolers:

ScreenShowsOne row per
AlertsAlerts raised on your coolers and how they were handled.Alert
CommandsCommands sent to devices, and whether they ran.Command
VisitsRecorded visits to coolers, and whether each cooler was found.Visit

Activity at a glance ​

Sample rows from the three screens. Alerts: alert time, type, priority, status and owner. Commands: command, value, result, who requested it and when it ran. Visits: visit time, visitor, status and location. Illustration with sample data.

Open the full-size activity diagram.

When to use it ​

  • To review the alerts on your coolers and how they were resolved.
  • To check whether a command reached a device and what it returned.
  • To confirm when a cooler was last visited, and whether it was where it should be.

Where to find it ​

Select Logs and then Alerts, Commands or Visits, under Telemetry Logs. The date range and table work as described in the Logs overview.

Access is role-based

Each of these screens is a separate permission in your role, so you might see some and not others. If a screen you need is missing, contact your administrator or CoolR Support.

Alerts ​

What it shows: every alert raised on your coolers in the date range, open or closed, with its owner and how it was handled. The list is read-only.

The Alerts screen: Status is New or Closed and Priority is Low, Medium or High. Each row shows the alert type and value, the owner, its age in days and how it was handled. A high-priority alert that is still new is highlighted. Illustration with sample data.

Open the full-size Alerts diagram.

Key features:

  • Status and priority: Status is New (open) or Closed. Priority is Low, Medium or High.
  • Ownership and age: Owner and Manager show who is responsible, and Age (Days) shows how long the alert has been open.
  • How it was handled: Diagnosis, Recommended Actions, Action Taken and Resolution record the follow-up. Snoozed Until shows the date until which an alert was put aside.
  • Kind of alert: Alert Category groups alerts, for example Business Alert or System Alert.
ColumnsWhat they show
Alert ID, Alert At, Alert Type, Alert Definition, Alert CategoryWhich alert was raised, and when.
Value, Unit, Alert TextThe reading or message that raised it.
Priority, Status, Owner, Manager, Age (Days)How urgent it is, who is responsible, and how long it has been open.
Diagnosis, Diagnosis Date, Recommended Actions, Action Taken, Resolution, Closed On, Snoozed UntilHow the alert was handled.
Asset Serial Number, Asset Type, Device Number, MDM Hub Serial Number, Image SourceThe cooler and device.

Commands ​

What it shows: every command sent to a device, such as reading its battery level, changing a camera setting or updating its firmware, and whether the device ran it and with what result.

The Commands screen: each row shows what was requested, by whom and when, when the device ran it and the result. A row with no Executed On is still waiting for the device. Illustration with sample data.

Open the full-size Commands diagram.

Key features:

  • Request and outcome on one row: Command, Requested By and Requested On show what was requested, by whom and when. Executed On and Result show when the device ran it and what it returned.
  • Pending commands: a blank Executed On means the device has not run the command yet.
  • Cancelled commands: Cancelled shows a command that was withdrawn before it ran.
  • Settings changes: Requested Configuration and Value show the setting that was asked for.
ColumnsWhat they show
Command, Requested Configuration, ValueWhat was requested.
Requested By, Requested OnWho requested it, and when.
Executed On, ResultWhen the device ran it, and the outcome.
Modified On, CancelledWhen the command was last updated, and whether it was cancelled.
Asset Serial Number, Device NumberThe cooler and device.

Visits ​

What it shows: every recorded visit to a cooler, with whether the cooler was found at its outlet.

The Visits screen: Status is Found, Missing or Wrong Location. Each row shows when the visit happened, who made it, where it was recorded and any notes. A cooler found at the wrong location is highlighted. Illustration with sample data.

Open the full-size Visits diagram.

Key features:

  • Was the cooler there? Status is Found, Missing or Wrong Location.
  • Who and when: Visited By and Visit Date Time show who made the visit and when.
  • Where it was recorded: Latitude and Longitude show where the visit was logged, along with the Displacement.
  • Notes: comments the visitor added.
ColumnsWhat they show
Asset Serial NumberThe cooler visited.
Visit Date Time, Visited ByWhen the visit happened, and who made it.
StatusFound, Missing or Wrong Location.
Latitude, Longitude, DisplacementWhere the visit was recorded.
NotesComments from the visit.

Why you might not see something ​

  • A screen is missing from the menu: your role does not include that screen. Contact your administrator or CoolR Support.
  • An alert is missing: it was raised outside the date range. The range applies to Alert At, not to when the alert was closed.
  • Executed On is blank: the device has not run the command yet.
  • A cooler has no visits: no visit was recorded for it in the date range.

Tips ​

  • Filter Alerts by Status to list the alerts still open, and sort by Age (Days) to see the oldest first.
  • Filter Commands for a blank Executed On to list commands still waiting for their device.
  • Filter Visits by Status to list coolers reported Missing or at the Wrong Location.

Last updated: November 16, 2026. Screens and options vary with your role and your organization's setup.