Project-Level Logs & Monitoring in AXQA
Logs & Monitoring in AXQA provide structured visibility into system activity and project-level execution behavior. Each project maintains its own isolated log stream, allowing teams to track events, diagnose issues, and maintain operational transparency.
Within the AXQA Execution Intelligence Platform, logs are structured, project-aware activity records that provide technical visibility without exposing unrelated data across workspaces.
Why it matters
- Helps identify execution or configuration issues quickly.
- Provides traceability for system activity.
- Supports debugging across automation and Smart Agent runs.
- Improves accountability and operational clarity.
Project-based log isolation
Every project in AXQA maintains its own dedicated log stream. This ensures clean separation between projects and prevents cross-project data exposure.
- Logs are scoped to a specific project.
- Users only see logs for projects they have access to.
- No global log visibility across unrelated projects.
Note
All log streams follow strict project-level permission enforcement. Users can only access logs for projects they are explicitly assigned to, ensuring controlled visibility and audit-ready traceability.
What logs capture
- Execution events.
- Automation triggers.
- Smart Agent activity.
- System-level events related to project operations.
Logs vs execution history
Execution History focuses on structured test results (Pass / Fail, steps, comparisons). Logs provide technical-level activity traces that help explain what happened behind the scenes.
How monitoring supports stability
- Detect unexpected behavior during execution.
- Validate automation runs.
- Investigate system anomalies.
- Support internal debugging workflows.
Note
Logs complement structured execution history by providing technical-level insight into automation triggers, validation flows, and system behavior during runtime.
Designed for clarity
Logs are structured for readability and filtering. They are not raw server dumps — they are project-aware activity records.
Best practices
- Review logs when diagnosing execution inconsistencies.
- Use filtering tools to isolate relevant events.
- Correlate logs with execution timestamps for faster troubleshooting.
- Audit logs regularly during heavy automation cycles.
Security & access
- Log visibility follows project permissions.
- No cross-project exposure is possible.
- Access is restricted to authorized users.
Related documentation
- Project Log Viewer
- Filtering & Searching Logs
- Execution History Overview
- Server Status & Storage Monitoring