How Can We Help?
You are here:
Print

Event Logs

Quick Overview

Event Logs in zAccess provide administrators with a detailed, timestamped record of all major system and user-triggered actions. These logs are critical for auditing, troubleshooting, and verifying the behavior of policy assignments, session events, and gateway activity. Event Logs serve as a forensic tool for diagnosing access issues and ensuring compliance with organizational policies.

How to Use This Feature in the UI

  1. Log in to the zAccess Director UI.
  2. Navigate to Event Logs in the left-hand navigation panel.
  3. The log viewer will display a sortable, filterable table of events, including:
    • Timestamp
    • Event Type (e.g., login, ruleset match, gateway selection)
    • Device/User Info
    • Result or Status (e.g., success, fail, timeout)
  4. Use filters at the top of the table to narrow the list by time range, event type, or specific user/device identifiers.

Concepts & Use Cases

  • Audit Trails: Track which policy was applied to which device, when, and under what conditions.
  • Troubleshooting Access Issues: Identify whether login failures or misapplied policies stem from ruleset conditions or network reachability.
  • Compliance Reporting: Provide documentation for security audits or regulatory requirements related to access control enforcement.
  • Gateway Diagnostics: Use log entries to verify gateway health, usage frequency, or failover behavior.

Troubleshooting & FAQs

  • Why am I not seeing any logs?
    Ensure event logging is enabled in system settings and that the zAccess agents are actively reporting session and policy events.
  • Can I export the logs?
    Yes, the Event Logs table supports CSV export. For automated export, backend configuration or API integration may be required.
  • What event types are logged?
    Common types include: user login, policy match, ruleset evaluation, session drop, gateway assignment, and connection health checks.
  • How can I trace a single session across logs?
    Use a consistent filter—such as MAC address, IP, or username—across the event log timeline to trace activity end-to-end.
Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
5
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents
Top