Wix stores each entry on the Logs page as a JSON object based on the OpenTelemetry log data model. You see this object in the entry's Log details panel, and you get it when you click Copy.
You don't write this object yourself. Wix builds it from the message, level, tags, and contexts that your code passes to the monitoring client, and adds the other fields. To write entries, see Write Log Messages in Studio Two.
This reference describes entries as they appear on the Logs page. Entries that Wix forwards to an OpenTelemetry endpoint are OpenTelemetry log records, so some fields differ. See Forward Logs to an OpenTelemetry Endpoint in Studio Two.
Date and time Wix received the entry, in ISO 8601 format with your browser's time zone offset. The Time column on the Logs page shows this value.
Time the logged event happened, in nanoseconds since the Unix epoch. For a message or a caught error, the time your code called the monitoring client. For an uncaught backend error, the time the error was thrown.
Time Wix received the entry, in nanoseconds since the Unix epoch. Same moment as createdDate.
Severity as an OpenTelemetry severity number.
Severity name that matches severityNumber.
Log message. For an error, the error's name followed by its message. For example, Error: Payment failed.
ID that Wix uses for your site's code. Every entry on your site's Logs page has the same value. It's the appId in your project's wix.config.mjs file.
Site ID.
Details about where the entry came from, plus the tags and contexts your code attached.
Each field appears only when it applies to the entry.
Details about the environment that wrote the entry.
Entries that Wix forwards to an OpenTelemetry endpoint also have wix.site.id and wix.app.id resource attributes, with the same values as siteId and appId.
The following call writes a warning with a tag and a context:
Wix stores the resulting entry as the following object:
Last updated: 2 November 2026