Activity Logs
Track every action taken during your event — timer starts, messages, session changes, and more. Activity Logs give you a complete audit trail of what happened, when, and who did it.
What Gets Logged
Tevyr automatically records over 40 different event types. Every significant action — whether triggered by a controller, by the system, or by an audience member — is captured with a timestamp and context.
| Category | Events tracked |
|---|---|
| Timer controls | Start, pause, reset, time adjustments (+/−), scrub (jump to a specific time) |
| Session lifecycle | Started, completed, skipped, created, edited, deleted, reordered, extended, overage recorded |
| Messages | Sent (with content), cleared |
| Effects | Blackout on/off, flash on/off, panic on/off, disco on/off |
| Questions | Received (with content), displayed on screen, dismissed, selected |
| Connections | Controller connected/disconnected, screen connected/disconnected |
| Scheduling | Event started, event completed, auto-play countdown started, scheduled start triggered, gap detected/resolved, conflict detected/resolved |
| Timing accuracy | Delay recorded, early start recorded, break started, break forwarded to audience |
| On-spot timers | Start, pause, reset |
| Macros | Created, updated, deleted, executed, execution failed, execution cancelled, schedule created/updated/deleted, schedule fired, schedule skipped |
Accessing Activity Logs
Open the Activity Logs modal from the controller. The modal shows a chronological list of all actions taken during the event, with the most recent entries at the top.
Real-Time Updates
Activity Logs refresh automatically every 5 seconds while the modal is open. A live indicator in the header confirms that real-time updates are active. Up to 500 log entries are displayed per session.
Log Entry Details
Each log entry contains:
| Field | Description | Example |
|---|---|---|
| Timestamp | When the action occurred, shown as relative time | Just now, 2m ago, 1h ago |
| Actor | Who or what performed the action | iOS App, Web Control, System, Audience |
| Activity | The type of action that was performed | timer_start, message_sent, session_completed |
| Session | The session associated with the action, if any | Opening Keynote |
| Description | A human-readable summary of what happened | Timer Started at 14:30 |
| Data | Additional context specific to the action type | Duration, content, adjustment amount |
Example Log Entries
[14:30:05] Web Control: Timer Started at 14:30
[14:32:12] Web Control: Time Added (+5s)
[14:35:00] iOS App: Message Sent: "5 minutes remaining"
[14:40:00] System: Session Completed — Opening Keynote
[14:40:01] System: Session Extended (Session ran 2m 30s over)
[14:40:05] Audience: Question Received: "When is the next break?"
Filtering
Filter logs to focus on specific sessions or controllers:
| Filter | Options | Use case |
|---|---|---|
| Session | All Sessions, No Session, or a specific session name | Review timing for a single presentation |
| Actor | All, iOS App, Web Control, System, Audience | See only actions from a specific controller or device |
Filters can be combined — for example, show only timer actions from the iOS App during the "Keynote" session.
Exporting Logs
Export your activity logs for post-event reporting, analysis, or archiving.
| Format | How it works | Output |
|---|---|---|
| CSV | Click the export button to download a CSV file. Respects current filters. | activity-logs-2026-03-27.csv |
| Clipboard | Click copy to clipboard. Logs are formatted as readable text. | [14:30:05] Web Control: Timer Started |
CSV Columns
The exported CSV file contains the following columns:
| Column | Description |
|---|---|
| Timestamp | ISO 8601 format (e.g., 2026-03-27T14:30:05.000Z) |
| Actor | The controller or system that performed the action |
| Activity | The machine-readable activity type (e.g., timer_start) |
| Session | The session name, if the action was session-specific |
| Description | Human-readable description of the action |
| Data | JSON-encoded metadata with additional context |
Export your activity logs after every event. The CSV format opens directly in Excel, Google Sheets, or any spreadsheet app — making it easy to create post-event reports, track timing accuracy, or share execution data with clients and stakeholders.
Common Use Cases
Post-event reporting
Review exact timing for every session — when it started, how long it ran, whether it went over. Share reports with event organizers and sponsors.
Debugging issues
Identify what happened when a screen went dark or a timer behaved unexpectedly. Trace actions back to a specific controller and timestamp.
Multi-controller accountability
When multiple operators control the same event, see exactly who made each change. Each action is tagged with the actor (iOS App, Web Control, System).
Client deliverables
Provide sponsors and stakeholders with concrete data — how many sessions ran on time, total event duration, and a full timeline of actions taken.
What gets logged
Every action — manual or system-generated — is captured with sub-second timestamps. Automatic events like session completions, gap detections, and scheduled starts are logged by the system alongside operator actions. All logs persist in the database and remain available for export after the event ends.