Event Logs
Event Logs is the audit-style activity feed for your RealTimeX instance. It is intended for operational review rather than conversation analysis, and access is restricted to admins.
What the page shows
Each entry includes:
- event name
- user
- occurred time
The page is paginated and shows the newest entries first.
Expand metadata when available
Some events include structured metadata. When metadata is present, you can expand the row and inspect the payload directly in the UI.
This is where most of the useful detail lives, especially for exports, updates, deletions, and integration-related actions.
What counts as an event
RealTimeX records many kinds of operational activity across the app. The exact event names vary by feature, but common examples include:
- authentication activity
- exports
- updates to settings or resources
- deletions
- workspace and integration actions
Treat the event name as the high-level label and the metadata panel as the detailed context.
Clearing the log
Admins can clear the event log from this page. That removes prior audit history and the system then records that the clear action happened, so the reset itself remains traceable.
Event Logs vs Chat Logs
Use Event Logs when you need operator or audit visibility. Use Chat Logs when you need the actual prompt and response content from recorded conversations.
Event Logs vs System Logs
Use Event Logs for audit-style product activity.
Use System Logs when you need technical log lines, subsystem sources, or structured debugging context from the app and server.