The log object contains messages and metadata about events and errors that occur on your site. Logs are generated by Wix, and with the exception of the payload message, their structure and data can't be modified.
It is important to understand log object structure for effective debugging and monitoring. The log object includes the following fields:
| Field | Type | Description |
|---|---|---|
id | string | Each log entry is assigned a unique ID. A log entry that has the same id as another log entry indicates a duplicate. |
insertId | string | Each log is assigned a unique ID. A log that has the same insertId as another log indicates a duplicate. |
timestamp | string | Time the log event occurred. Date string in ISO 8601 date format. |
receiveTimestamp | string | Time the log was received by Wix Logs or the external monitoring tool. Date string in ISO 8601 date format. |
severity | string | Severity of the log. Possible values: INFO: Status, performance, or other general information. WARNING: An unexpected or undesired development that may cause problems. ERROR: A serious issue likely to cause problems. DEBUG: Logs that are only useful while debugging and generally not relevant for production. |
labels | object | Additional information about the log. |
labels.siteUrl | string | Base URL of the site associated with the log. |
labels.namespace | string | Name of Wix app associated with the log, such as Wix Stores or Wix Bookings. The generic namespace Velo represents site code not associated with any specific Wix app. Only the Velo namespace is supported. You currently can't enter the name of any other Wix app. |
labels.tenantId | GUID | Unique site identifier. Does not change even if the site name or other site parameters change. |
labels.viewMode | string | Viewing mode in which the log originated. Possible values: Preview: Site preview mode. Site: Published site. |
labels.revision | string | Unique site revision identifier. You can use the revision property together with the Release Manager to monitor and debug new site revisions. |
operation | object | Additional information about a potentially long-running operation associated with the log. |
operation.id | string | Unique operation identifier. |
operation.producer | string | Operation context, such as the page or web module where the operation took place. |
sourceLocation | object | Source code location information. Applies to backend log entries with the Velo namespace. |
sourceLocation.file | string | File that generated the log. |
sourceLocation.line | number | Number of line that generated the log. |
sourceLocation.column | number | Number of the column on the line that generated the log. |
jsonPayload | object | Log payload in JSON format. |
jsonPayload.message | string | Payload message. |
Some operations, such as a method call or a scheduled job, generate multiple log entries. The operation object allows you to find the logs associated with a specific operation. Use the unique operation.id field to identify which operation generated the logs, and the producer property to view the context in which the operation took place.
Here's an example log object: