public-data-docs

Table: EVENTS

Description:

Logs significant system and user-related events within the Wunder platform. Events may be tied to users, vehicles, bookings, rentals, and various backend processes.

🔑 Primary Key

id

Field Name Data Type Description
id NUMBER Unique identifier for the event.
position GEOMETRY Geolocation associated with the event.
vehicle_position GEOMETRY Specific vehicle location at the time of the event (may differ from position).
type NUMBER Event type code indicating the nature of the event. (1 => APP_LOGIN. 181 => RENTAL_START_BLUETOOTH. 182 => RENTAL_END_BLUETOOTH. 156 => RENTAL_START_RFID. 138 => RENTAL_END_RFID. 90 => VEHICLE_SERVICE_STATE_V2_FUNCTIONAL. 91 => VEHICLE_SERVICE_STATE_V2_INSPECT. 92 => VEHICLE_SERVICE_STATE_V2_RELOCATE. 93 => VEHICLE_SERVICE_STATE_V2_COLLECT. 94 => VEHICLE_SERVICE_STATE_V2_SERVICE_ON_SITE. 95 => VEHICLE_SERVICE_STATE_V2_SERVICE_WORKSHOP. 96 => VEHICLE_SERVICE_STATE_V2_SERVICE_EXTERNAL. 97 => VEHICLE_SERVICE_STATE_V2_REPLACE. 98 => VEHICLE_SERVICE_STATE_V2_IMPOUNDED. 188 => VEHICLE_SERVICE_STATE_V2_DEFLEETED. 122 => VEHICLE_BATTERY_LEVEL_LOW. 121 => VEHICLE_BATTERY_LEVEL_CRITICAL. 120 => VEHICLE_BATTERY_LEVEL_UNKNOWN. 123 => VEHICLE_BATTERY_LEVEL_MEDIUM) The type uses non-sequential integers; see the full mapping in core-service EventType.
event_type_name TEXT String label for type.
guser_id NUMBER ID of the user (guser) associated with the event.
rental_id NUMBER Rental ID if the event is tied to a specific rental.
booking_id NUMBER Booking ID if the event is tied to a specific booking.
message_id NUMBER ID of the message associated with the event, if applicable.
balance_id NUMBER Associated balance entry ID if the event involves a balance change.
error TEXT Human-readable error message, if the event was error-related.
internal_message TEXT System/internal notes or messages relevant to the event.
admin_guser_id NUMBER Admin user ID who triggered or is linked to the event.
vehicle_id NUMBER ID of the vehicle involved in the event.
created_at TIMESTAMP_TZ Timestamp when the event was recorded.
radar_id NUMBER Radar or sensor ID that registered the event, if applicable.
request_info VARIANT Raw request data or context related to the event (e.g., headers, parameters).
branch_id NUMBER Branch location associated with the event.
details VARIANT Structured JSON field holding any additional details specific to the event. Transaction related. Example: { “chargeAmount”: 4.58, “chargeId”: “166946034”, “declinedCode”: “BE2006 - DECLINED - Insufficient Funds” }
trace_id TEXT Distributed trace ID for request tracing and debugging across systems.
physical_station_slot_id NUMBER ID of the physical station slot involved in the event, if applicable.
is_debug BOOLEAN Indicates whether the event was emitted in a debug context.
_snowflake_inserted_at TIMESTAMP_NTZ System timestamp when the record was inserted into Snowflake.
_snowflake_updated_at TIMESTAMP_NTZ System timestamp when the record was last updated in Snowflake.
_snowflake_deleted BOOLEAN True if the record was deleted in the source.