The purpose of Audit Logs is to capture changes to the UXI configuration. The messages include a log UID, timestamp, a description of the change, the user who made the change, and the change that was made.
Audit Log Schema
The audit log schema is the same format for all audit logs. Some fields may contain null values if not applicable.
Name | Type | Comments |
uid | string | The audit log message uid. |
customer_uid | string | Customer uid |
description | string | Short description of the change |
subject | string | The entity that made the change |
subject_type | string | The type of entity that made the change |
subject_id | string | The id of entity that made the change |
object | string | The object type that was changed |
object_type | string | The object type that was changed |
object_id | string | The id of the object that was changed |
action | string | The action performed on the object |
data | json nested string | The change that was made |
timestamp | datetime | timestamp in (UTC time) |
Here is a sample message of the audit log format:
{
"uid": "e0279a49-a18d-4504-a40a-0620a5ab1208",
"customer_uid": "<customer_uid>",
"description": "Sensor group updated",
"subject": "<user email that made the change>",
"subject_type": "user",
"subject_id": "<user-id>",
"object": "sensor-group-assignment",
"object_type": "sensor_group_assignment",
"object_id": "<object-uid>",
"action": "update",
"data": "{\"updated_to\": {\"group_uid\": \"dc89c20e08c0\", \"group_name\": \"Singapore\", \"group_path\": \"25a2f3797a71.879a3e11f9ca.240b48bdd17f.dc89c20e08c0\", \"sensor_uid\": \"8941ca38-4759-4b59-b32b-9e1fa93c6e58\"}, \"updated_from\": {\"group_uid\": \"36a88f258472\", \"group_name\": \"Tokyo\", \"group_path\": \"25a2f3797a71.879a3e11f9ca.1d194673d5eb.36a88f258472\", \"sensor_uid\": \"8941ca38-4759-4b59-b32b-9e1fa93c6e58\"}}",
"meta": "{}",
"timestamp": "2025-08-27T00:06:11"
}