Activity Logs

Horuph Studio Usage Guide Version 1.0.0

What It Is

Activity Logs records important actions performed in the admin panel (and other system actions, if enabled). It is mainly used for auditing, debugging, and tracking changes over time.

Tabs

• Activity Logs: View the recorded logs and open full details.
• Settings: Control what gets logged, how long logs are kept, and which fields are hidden.

Activity Logs Tab

This tab shows your recent activity entries. Each row represents one action that the system recorded.

• Time: When the action happened.
• Open Details: Use the row action (for example the “view” icon) to open the full log entry.
• Empty State: If you see “No logs found”, it usually means logging is disabled, filters are active, or there simply were no actions yet.

Activity Log Details

Opening a log entry shows a detailed view (modal/panel) with multiple sections:

Basic Information

• ID: Unique log identifier.
• Time: Exact timestamp of the action.
• Action: Action name/key (example: media-file-delete).
• Status: Success / Failed (based on the action result).
• Path: Request path that triggered the action.

User Information

• User: The account that performed the action.
• User ID: Internal user identifier.

Request Information

• IP Address: The requester IP.
• User Agent: Browser/device information.

Payload / Result

• Query Parameters: The query string parameters (if any).
• Response Message: The returned message (example: “File deleted successfully”).
• Full JSON: A complete structured snapshot of the request/response (with sensitive values redacted).

Settings Tab

Enable Logging

Turn logging on/off for the entire system. If disabled, no new logs will be stored until it is re-enabled.

Log Retention

Defines how long logs are kept in the database (example: 7 days). After the retention period, older logs are deleted automatically.

Actions List

This section controls which actions are recorded. Use the checklist to include/exclude actions from being logged.

• Search in Actions: Quickly find an action by name.
• Checklist: Select which actions should be logged (unchecked actions are excluded).
• Tip: Keep logging enabled for security-sensitive and content-changing actions, and disable noisy actions if you don’t need them.

Sensitive Fields (Hidden from Logs)

This is a safety layer. Any matching keys (for example password, token, api_key, etc.) will be redacted from the log payload shown in details.

• Add Field: Add a new key name to redact.
• Remove: Remove a key if you want it visible (not recommended for secrets).

Delete All Logs

Deletes all existing activity logs from the database. Use this only when you intentionally want to clear history (for example: after development/testing).

Save Changes

Apply your settings. Changes affect new logs going forward (existing logs remain as they are).

Best Practices

• Don’t log secrets: Keep “Sensitive Fields” updated (passwords, tokens, keys, license values, etc.).
• Retention matters: Set a retention window that fits your needs and your database size.
• Keep it useful: Exclude actions that generate too much noise, but keep critical actions logged.
• Use logs for debugging: When something “mysteriously” changes, logs usually show who/when/what.