Audit Logs for Trigger Variable

The trigger variables audit log system tracks all override operations performed on trigger configuration parameters across different hierarchical levels. It captures when and how trigger settings are customized or reverted at tenant, group, or endpoint levels.

Each audit entry records:

  • The specific variable being modified (like PRE_BUFFER, POST_BUFFER, etc.)
  • Whether a new override is being set (ASSIGN) or removed (UNASSIGN)
  • The level at which the change is made (tenant, group, or endpoint)
  • The previous and new values of the variable

Overview

Trigger Variables audit logs track all override operations performed on trigger configuration variables. These logs capture when variables are assigned (overridden) at different hierarchical levels (tenant, group, or endpoint) or unassigned (removing override).

Audit Details

Auditable Resource

  • TRIGGER_VARIABLE

Auditable Actions

  • ASSIGN: When a variable is overridden with a new value at a specific level
  • UNASSIGN: When an override is removed, causing the value to be inherited from a higher level in the hierarchy

Common Resource Names (Variables)

Variable NameDescription
ENABLE_TRIGGEREnable/disable the trigger
PRE_BUFFERPre-event recording duration
POST_BUFFERPost-event recording duration
COOL_DOWN_ENABLEDEnable/disable cool-down period
COOL_DOWN_TIMERDuration of cool-down period
CHIMEDifferent Chimes to be played
MEDIA_TYPEType of media to record
UPLOAD_STRATEGYStrategy for uploading recorded media (ON CLOUD or SD_CARD)
ENABLE_TTSEnable/disable Text-to-Speech

Example Audit Log Entries

Assigning a Variable Override

{
    "auditableResource": "TRIGGER_VARIABLE",
    "auditableAction": "ASSIGN",
    "resourceName": "PRE_BUFFER",
    "additionalMetadata": "{
        \"tenantName\": \"TenantA\",
        \"endpointId\": 1,
        \"deviceSerialNumber\": \"DEVICE123\",
        \"triggerCategoryName\": \"Tailgating\",
        \"targetLevel\": \"ENDPOINT\",
        \"targetLevelName\": \"1\"
    }",
    "previousState": "{\"value\": \"1.5\"}",
    "newState": "{\"value\": \"2.0\"}"
}

Removing a Variable Override

{
    "auditableResource": "TRIGGER_VARIABLE",
    "auditableAction": "UNASSIGN",
    "resourceName": "COOL_DOWN_TIMER",
    "additionalMetadata": "{
        \"tenantName\": \"TenantA\",
        \"endpointId\": 1,
        \"deviceSerialNumber\": \"DEVICE123\",
        \"triggerCategoryName\": \"Tailgating\",
        \"targetLevel\": \"GROUP\",
        \"targetLevelName\": \"GroupA\"
    }",
    "previousState": "{\"value\": \"30\"}",
    "newState": null
}

Additional Metadata Details

The additionalMetadata field contains:

  • tenantName: Name of the tenant
  • endpointId: ID of the endpoint (when applicable)
  • deviceSerialNumber: Serial number of the device
  • triggerCategoryName: Category of the trigger (e.g., "Tailgating")
  • targetLevel: Level where override is applied ("TENANT", "GROUP", or "ENDPOINT")
  • targetLevelName: Name/ID of the specific target level

State Information

  • previousState: JSON string containing the previous value (null for newly override value)
  • newState: JSON string containing the new value (null for UNASSIGN)
  • Values are wrapped in a JSON object with a "value" key
  • Example: {"value": "2.0"}

Override Hierarchy

When an override is unassigned, the effective value reverts to the nearest defined value in the hierarchy:

  1. Endpoint level
  2. Group level
  3. Tenant level
  4. Parent Tenant Levels ... (if any)
  5. Default system value
Language
Credentials
Header
Click Try It! to start a request and see the response here!