Allo Dashboard Reports and Logs for Administrators
View and filter message delivery events, device activity, and user actions in the dashboard to support post-exercise review and incident analysis.
The Allo dashboard records a log of significant events across your organisation's network — messages sent and delivered, devices joining and leaving the mesh, users logging in or accepting invitations, and more. These logs are the primary tool for evaluating how your deployment performed during an exercise or live incident, identifying delivery failures, and building reports for after-action reviews.
Logs and post-exercise delivery evaluation are currently in the pilot phase. The level of detail available may develop as the feature matures. If you need specific log data for an exercise and are unsure whether it is captured, contact your Allo point of contact before the exercise.
What the logs capture
The dashboard records events across three main categories.
Message delivery events
Every time a message is submitted to the radio network, the dashboard records:
- Timestamp — When the message was sent.
- Sender — The user who sent the message.
- Recipient or group — Who the message was addressed to.
- Delivery status — Whether the message was delivered, pending, or failed to reach the recipient.
- Route information — In some cases, which devices or repeaters relayed the message through the mesh.
For private messages, the log includes an acknowledgement status — whether the recipient's device confirmed receipt. For group messages, the log reflects network-level delivery rather than per-recipient confirmation.
Device activity
The logs record when devices connect to and disconnect from the mesh, when a device is paired with a phone for the first time, and when a device has not been seen on the network for an extended period. This helps you identify devices that were powered off or out of range during a deployment.
User actions
Administrative actions taken in the dashboard are also recorded — for example, when a user is invited or removed, when a device is provisioned or decommissioned, and when group membership changes. This provides an audit trail for your organisation's configuration history.
View the logs
- Log in to the dashboard and navigate to Reports & Logs (or Logs) in the sidebar.
- The log view shows events in reverse chronological order — most recent first.
- Each row shows the timestamp, event type, affected user or device, and a brief description.
- Click any row to expand it and see full details.
Filter the logs
For large deployments or long exercises, the full log can be lengthy. Use the filter tools to narrow it down.
Set a start date and end date to view only events that occurred during a specific time window. This is the most useful filter for post-exercise review — set the window to the start and end time of your exercise to see everything that happened during it.
Post-exercise review
After a training exercise or pilot deployment, the logs give you the evidence to answer key questions:
- Did all participants successfully send and receive messages?
- Were there any delivery failures, and if so, which users or devices were affected?
- Were there coverage gaps — areas where devices could not reach the mesh?
- Did all devices stay active throughout the exercise, or did some go offline unexpectedly?
- Were messages delivered within an acceptable time window?
Set the date range
Open the logs and set the filter to the exact start and end time of the exercise. This isolates exercise traffic from any background activity.
Review message delivery events
Look for any messages with a failed or undelivered status. Note the sender, recipient, and time so you can follow up with those participants.
Check device activity
Confirm that all registered devices were active during the exercise period. Any device shown as inactive during the window may indicate a power, Bluetooth, or coverage issue.
Identify coverage gaps
If a cluster of delivery failures involves users in the same physical area, this may point to a repeater placement issue. Cross-reference with your repeater placement plan.
Export or document findings
Record your findings — for example, by exporting the filtered log view or taking screenshots — and include them in your after-action report. See After an Exercise for a full evaluation checklist.
Before an exercise, agree with your team on what a successful delivery looks like and which metrics matter most. Knowing what you want to measure in advance makes post-exercise log analysis much faster.
Frequently asked questions
How long are logs retained?
Log retention policy is configured per organisation and may vary depending on your deployment agreement. Contact your Allo point of contact to confirm how long historical data is available for your organisation.
Can I export log data?
Export functionality is part of the reporting roadmap. In the current pilot phase, you can review logs in the dashboard and document findings manually. If you need automated exports for your organisation's reporting system, raise this with your Allo contact.
Can standard users view logs?
No. Log access is restricted to administrators. Standard users can see the delivery status of their own messages in the app, but they cannot access the organisation-wide log view in the dashboard.
Do logs capture message content?
The logs focus on delivery metadata — who sent a message, when, to whom, and whether it was delivered. Whether message content is stored or logged depends on your organisation's configuration. Consult your Allo point of contact and your organisation's data-handling policies. See also Privacy.
A device shows as inactive during an exercise — what does that mean?
It means the device either was not powered on, lost its Bluetooth connection to the paired phone, or was out of range of the mesh for that period. Check with the user assigned to that device to understand what happened. For recurring issues, see Bluetooth Connection Problems or Poor Range.