Project-Level Log Viewer in AXQA

The Project Log Viewer provides a clear, project-specific view of operational and execution activity. It helps teams understand what happened inside a project over time — whether during automation, Smart Agent execution, or general system activity.

Within the AXQA Execution Intelligence Platform, the Project Log Viewer provides structured, project-aware logging that supports troubleshooting, automation validation, and secure operational monitoring.

Why it matters

• Makes troubleshooting faster and more structured.
• Provides a reliable trace of project activity.
• Helps correlate issues with specific execution moments.
• Supports monitoring during high-volume testing periods.

Project-scoped by design

Each project has its own log stream. This keeps data separated, readable, and safe.

• Logs belong to a specific project.
• You will only see logs for projects you have access to.
• No cross-project mixing of events.

What you’ll see in the log viewer

• Timestamped log entries.
• Clear message descriptions.
• Event categories (based on the source of the activity).
• Execution-related context when available.

The goal is clarity: the log viewer is designed to be readable and useful, not overwhelming.

Common scenarios where logs help

• A test case ran but returned unexpected behavior.
• An automation rule triggered and you want to confirm timing.
• A Smart Agent execution appears delayed or incomplete.
• You need to understand what occurred before a failure.

How it works

1. Open the project you want to monitor.
2. Navigate to the Log Viewer section.
3. Review log entries in chronological order.
4. Use filtering and search to narrow down relevant events.
5. Correlate entries with execution history if needed.

Best practices

• Start with the timestamp closest to the issue you’re investigating.
• Use filters to isolate automation or agent-related activity.
• Compare logs with execution reports for full context.
• During release cycles, monitor logs regularly to catch issues early.

Common mistakes

❌ Trying to debug without checking timestamps
✔ Always correlate logs with the time the issue occurred.

❌ Assuming logs replace execution reports
✔ Use logs for technical tracing, and execution reports for test results.

Security & access

• Log access follows project-level permissions.
• Logs are isolated per project to prevent exposure.
• Only authorized users can view project logs.

Related documentation

• Logs & Monitoring Overview
• Filtering & Searching Logs
• Execution History Overview