Overview

System logs provide a chronological record of every significant action that happens at your property. When a booking is created, a guest checks in, a payment is recorded, or a setting is changed, Vesta logs the event with details about who did it, when, and what changed.

Logs are essential for troubleshooting (“Why was this booking cancelled?”), auditing (“Who changed the rate plan last week?”), and understanding patterns in your property’s operations.

Viewing Logs

Go to Settings > System Logs
The log table shows events in reverse chronological order (newest first)

Each log entry displays:

Column	What It Shows
Timestamp	When the event occurred
Level	Severity badge: Info (blue), Warning (yellow), or Error (red)
Event Type	The type of action (e.g., `booking.created`, `payment.recorded`)
Message	A human-readable summary of what happened
User	Who performed the action (if applicable)
View	Button to see full details

Filtering Logs

With potentially hundreds of events per day, filtering helps you find what you need:

Date Range — narrow down to a specific time period
Event Type — filter to a specific type of action (over 50 event types are tracked)
Severity Level — show only Info, Warning, or Error entries
Message Search — search within log messages for specific text (e.g., a guest name or room number)

:::tip When troubleshooting an issue, start by filtering to the relevant date and event type. For example, to investigate a missing payment, filter to the date in question and the payment event type. :::

Log Detail View

Click View on any log entry to open a detail modal with full information:

Event Type and Timestamp
Message — the full description
User — who triggered the event
Entity Type and ID — the record that was affected (e.g., Booking #42)
Request Data — the technical details of the action (JSON format)
Extra Metadata — additional context captured at the time of the event

:::info The request data and metadata fields contain technical details that are most useful for debugging. In day-to-day use, the message and entity information are usually sufficient. :::

Common Use Cases

“Who cancelled this booking?”

Filter by event type booking.cancelled and search for the booking confirmation number or guest name

“What happened during last night’s shift?”

Set the date range to cover the shift hours and browse chronologically

“Why did a payment fail?”

Filter by event type payment and severity Error to find failed payment events with error details

“What changes were made to rates?”

Filter by event types related to rate plans or calendar changes

Troubleshooting

Logs seem incomplete?

System logs are typically retained for about 90 days. Your organization can configure retention and may periodically clean up older logs
Some actions (like viewing a page) are not logged — only significant actions that change data

Cannot find a specific event?

Try broadening your filters. If you are too specific with the event type, you might miss related events
Use message search to look for names, numbers, or keywords across all event types

:::permissions System logs are visible to property members (property-scoped audit trail). Admins can also view logs across all properties from the admin area. :::

Property Settings — other property configuration options
Managing Roles and Permissions — controlling who can access logs