Activity Logs Not Showing Data
Activity Logs Not Showing Data
KyberGate's activity logs show real-time browsing activity, blocked requests, and filtering events for all managed
devices. If your activity logs appear empty or incomplete, this guide will help you identify and resolve the issue.
How Activity Logging Works
When a managed device browses the web:
1. Traffic routes through the KyberGate proxy (via the PAC file)
2. The proxy evaluates the request against your filtering policies
3. The request is logged to Google Cloud Firestore in real-time
4. The admin dashboard queries Firestore to display activity logs
If any step in this pipeline is disrupted, logs will not appear.
Common Causes and Solutions
1. PAC File Not Applied to the Device
The PAC (Proxy Auto-Configuration) file tells the device to route traffic through KyberGate. Without it, traffic
bypasses the proxy entirely and nothing is logged.
How to check:
1. On the device, go to Settings → Wi-Fi → [Network Name] → Configure Proxy
2. Verify it's set to Automatic with the KyberGate PAC URL
3. The PAC URL should look like: https://proxy.kybergate.com/pac/YOUR-ORG-ID
How to fix:
- Redeploy the PAC profile via MDM
- For iPads: Check Settings → VPN & Device Management for the KyberGate profile
- For Chromebooks: Verify the PAC URL in Google Admin Console under Network Settings
2. Device Not Registered in KyberGate
Devices must be registered (enrolled) in your KyberGate dashboard to appear in logs.
How to check:
1. Go to Devices → All Devices in the admin dashboard
2. Search for the device by name, serial number, or user
3. If the device is missing, it hasn't been enrolled
How to fix:
- Ensure the MDM profile containing the KyberGate configuration is deployed to the device
- For manual enrollment, go to Devices → Add Device and follow the steps
- Verify the device's serial number matches what's in your MDM
3. Firestore Timeouts or Quota Issues
KyberGate stores logs in Google Cloud Firestore. Under heavy load or if quotas are exceeded, log writes may fail
silently.
How to check:
1. Go to Settings → System Status in the dashboard
2. Look for any Firestore connection warnings (yellow or red indicators)
3. Check if logs appear intermittently (some entries missing, but not all)
How to fix:
- Wait 15-30 minutes — transient Firestore issues usually resolve automatically
- If persistent, contact KyberGate support to check your Firestore quota
- Large districts (5,000+ devices) may need Firestore capacity upgrades
4. Bypass Domains Excluding Traffic
Certain domains are configured to bypass the proxy entirely (e.g., video conferencing, speed tests). Traffic to bypass
domains is not logged.
How to check:
1. Go to Settings → Proxy → Bypass Domains
2. Review the list of domains that skip the proxy
3. Common bypass entries: *.zoom.us, *.teams.microsoft.com, *.speedtest.net
How to fix:
- If you need logging for a bypassed domain, remove it from the bypass list
- Be cautious: removing video conferencing bypasses may cause performance issues
- Consider using the Chrome extension for visibility into bypassed HTTPS traffic
5. Time Range or Filter Mismatch
The dashboard may be showing the wrong time range or filtered to specific users/devices.
How to check:
1. In Activity Logs, check the date range selector in the top right
2. Verify no user, device, or category filters are active
3. Click Clear All Filters to reset the view
How to fix:
- Set the date range to Today or Last 24 Hours
- Remove any active filters
- Check your timezone setting in Settings → General matches your local timezone
6. Chrome Extension Not Active
If you rely on the KyberGate Chrome extension for logging on Chromebooks, ensure it's installed and active.
How to check:
1. On the Chromebook, go to chrome://extensions
2. Look for KyberGate (v2.7.1)
3. Verify it's enabled and not showing errors
How to fix:
- Force-install the extension via Google Admin Console
- See "Chrome Extension Troubleshooting" for detailed steps
Tips
- Test with a single device — When debugging, focus on one device and verify logs appear for it before checking others
- Use real-time view — The Activity Logs Live tab shows events as they happen, making it easy to test immediately
- Check proxy connectivity — On the device, visit http://proxy.kybergate.com/health — a successful response confirms
proxy connectivity
- Export logs — If logs exist but seem incomplete, export to CSV and check for gaps in timestamps
- Browser matters — Only traffic routed through the proxy is logged; apps that don't respect the system proxy (some
native apps) may not appear
Troubleshooting Quick Reference
| Symptom | Likely Cause | Solution | |---------|-------------|----------| | No logs at all | PAC not applied | Redeploy
MDM proxy profile | | Logs for some devices but not others | Specific devices not enrolled | Check device enrollment
status | | Intermittent missing logs | Firestore timeouts | Wait or contact support for quota check | | Specific sites
not logged | Bypass domains | Review bypass list in Settings | | Logs suddenly stopped | Proxy service issue | Check
System Status page |
Related Articles
- Device Enrollment and PAC Configuration
- Chrome Extension Troubleshooting
- Managing Content Filtering Policies