Activity log overview
The Activity log in NeoSpace NeoData is the place where authorized users review audit-style events related to platform usage: who did what, through which channel, against which resources, and whether the action succeeded. It supports governance, security reviews, and operational troubleshooting without replacing your organization’s central log warehouse.
Access depends on your role and tenant policies. If you cannot open the activity log, contact your NeoSpace administrator. For authentication and authorization concepts, see Authentication and authorization concept and the Permission guide.
What you can expect to see
Each row generally represents a recorded event. Typical columns include:
| Column | Purpose |
|---|---|
| Event | High-level description of what occurred. |
| Event type | Category that helps group similar actions for filtering. |
| Action | Specific operation (for example create, update, delete). |
| Status | Outcome such as success or failure when applicable. |
| Source | Whether the call came from an interactive user session or an API key / automation path. |
| User | Identity associated with the event when available. |
| API | Identifier or route context for programmatic access. |
| Event date | Timestamp in your expected timezone context (confirm with your administrator if you need UTC versus local display). |
Opening a row (when the product provides a details view) may reveal additional metadata, tenant context, and identifiers useful for support tickets.
Filtering and search
Use the filters at the top of the list to narrow events by:
- Status, action, and event type
- Time range (start and end)
- Free-text search where supported—often aligned to resource identifiers when you paste an ID from another screen
Large tenants produce many events; always scope by date first for faster results.
NeoData versus cluster activity
NeoData exposes an Activity log entry under Monitoring in the NeoData sidebar. Separately, cluster views may include their own history or diagnostics. Use NeoData activity for platform and API usage tied to your space; use cluster pages for infrastructure-centric events when your subscription includes clusters.
Governance practices
- Least privilege: Grant activity log access only to roles that need visibility for compliance or operations.
- Incident response: When investigating an issue, capture event identifiers and timestamps before making configuration changes.
- Retention: Long-term retention and export policies are defined by your agreement with NeoSpace; confirm with your administrator.
Screenshots (product captures)
Store files under static/img/activity-log/.