Overseer

Common Issues & Troubleshooting for Overseer

Support
•Last updated: February 16, 2026

Welcome to the comprehensive troubleshooting guide for Overseer, your macOS system monitoring dashboard. This guide helps you identify and resolve the most common issues encountered while monitoring your Mac's performance.

How to Use This Guide

  1. Identify your issue from the categories below
  2. Follow the troubleshooting steps in order
  3. Try the solutions until the issue is resolved
  4. If still unresolved, use the "Contacting Support" section

Quick Reference: Common Issues

| Issue | Likely Cause | Quick Solution | | --------------------------- | ------------------------------------- | ----------------------------------------- | | Missing system metrics | Permissions not granted | Grant System Monitoring permission | | High CPU usage by Overseer | Too frequent updates or many metrics | Reduce update frequency, disable metrics | | No notifications/alerts | macOS Notification Center settings | Check Focus modes, allow notifications | | Export fails | Permission issues, disk full | Check file permissions, free disk space | | GPU/temp metrics missing | Hardware compatibility, macOS version | Update macOS, check hardware support | | Network shows zero | Network permission missing | Grant Network permission in Privacy | | Battery not showing | Desktop Mac or missing sensors | Check hardware compatibility | | UI feels sluggish | System resource constraints | Close other apps, restart Overseer |

Permission Issues

"Overseer cannot monitor system metrics" or Limited Metrics Available

Symptoms:

  • CPU/memory metrics show "No Data" or "Permission Required"
  • Only basic metrics available
  • "Grant Permission" prompts appearing

Step-by-Step Troubleshooting:

  1. Grant System Monitoring Permission:

    • Go to System Settings → Privacy & Security → System Monitoring
    • Find Overseer in the list and ensure it's checked ✅
    • If not listed, click the + button and add Overseer from Applications
    • Restart Overseer after granting permission

  2. Grant Disk Access Permission (for disk usage monitoring):

    • System Settings → Privacy & Security → Files and Folders
    • Add Overseer and grant access to necessary volumes
    • Typically needed for disk I/O, SMART status, and storage monitoring

  3. Grant Network Access Permission (for network monitoring):

    • System Settings → Privacy & Security → Network
    • Ensure Overseer is allowed to monitor network activity
    • Required for bandwidth usage, network traffic, and connection monitoring

  4. Optional: Accessibility Access (for enhanced process monitoring):

    • System Settings → Privacy & Security → Accessibility
    • Add Overseer for detailed process insights and application monitoring
    • Can be declined; basic process monitoring will still work

Verification Steps:

  1. Close and restart Overseer completely
  2. Check if metrics start appearing within 30 seconds
  3. If still missing, check Console.app for permission-related errors

Missing Hardware Sensors or Metrics

GPU, Temperature, or Battery Metrics Not Showing

Symptoms:

  • GPU utilization shows 0% or "Not Available"
  • Temperature sensors missing or showing "--"
  • Battery health/percentage not displayed
  • Specific hardware metrics unavailable

Step-by-Step Troubleshooting:

  1. Check macOS Version Compatibility:

    • Some advanced metrics require macOS 14.0 (Sonoma) or later
    • Go to Apple menu → About This Mac to check your version
    • Update macOS if needed via System Settings → General → Software Update

  2. Verify Hardware Compatibility:

    • Apple Silicon Macs (M1/M2/M3): Full sensor support including GPU, temperature, battery
    • Intel Macs (2018+): Good sensor support, varies by model
    • Older Intel Macs: Limited sensor availability, especially for temperature
    • Check your Mac model: Apple menu → About This Mac → System Report → Hardware

  3. Grant All Required Permissions (see Permission Issues section above)

  4. Restart Overseer after permission changes

  5. Check for Overseer Updates:

    • Overseer → Check for Updates (direct download version)
    • App Store → Updates (Mac App Store version)
    • New sensor support is regularly added in updates

Specific Hardware Checks:

  • GPU Monitoring: Requires Apple Silicon or discrete GPU (AMD/NVIDIA)
  • Temperature Sensors: More available on MacBook Pro, iMac Pro, Mac Studio
  • Battery Metrics: Only available on MacBooks, MacBook Air, MacBook Pro
  • Desktop Macs: No battery metrics (expected)

Performance Issues: Overseer Using High CPU or Memory

Symptoms:

  • Overseer itself shows high CPU usage in Activity Monitor
  • System feels sluggish when Overseer is running
  • High memory consumption by Overseer
  • Fans spinning up when using Overseer

Step-by-Step Troubleshooting:

  1. Reduce Monitoring Frequency:

    • Go to Preferences → Performance in Overseer
    • Increase the update interval:
      • Real-time: 1 second (highest CPU)
      • Fast: 2-3 seconds (balanced)
      • Standard: 5 seconds (recommended)
      • Economical: 10+ seconds (lowest CPU)

  2. Disable Unnecessary Metrics:

    • Customize your dashboard to show only needed metrics
    • Disable GPU monitoring if not needed
    • Turn off network monitoring when not required
    • Reduce historical data retention in Preferences

  3. Check for Conflicting Monitoring Tools:

    • Close other system monitoring apps (iStat Menus, Activity Monitor tabs, etc.)
    • Disable competing monitoring menu bar items
    • Check for antivirus/security software that may interfere

  4. Optimize Dashboard Configuration:

    • Reduce number of active graphs/charts
    • Use simpler visualization types (bars instead of detailed graphs)
    • Disable animation effects in Preferences → Appearance

  5. System-Wide Checks:

    • Ensure sufficient RAM (16GB+ recommended for intensive monitoring)
    • Check for macOS updates that may improve performance
    • Restart your Mac to clear system caches

If High CPU Persists:

  1. Create a new, minimal dashboard with just 1-2 metrics
  2. Gradually add metrics back to identify which causes high CPU
  3. Check Console.app for Overseer-related errors
  4. Reset Overseer preferences (see Advanced Troubleshooting below)

Notification Issues

Alerts Not Appearing in macOS Notification Center

Symptoms:

  • Threshold alerts don't trigger notifications
  • No banners or alerts appear
  • Notifications appear inconsistently
  • "Test Alert" works but real alerts don't

Step-by-Step Troubleshooting:

  1. Check macOS Notification Settings:

    • System Settings → Notifications → Overseer
    • Ensure "Allow Notifications" is enabled
    • Set notification style to Banners or Alerts (not None)
    • Check "Show in Notification Center" is enabled

  2. Verify Focus Modes:

    • Focus modes (Do Not Disturb, Work, Sleep, etc.) suppress notifications
    • Check System Settings → Focus
    • Ensure Overseer is allowed through Focus modes:
      • Edit each Focus mode → Apps → Allow Notifications From → Add Overseer

  3. Test Alert Configuration:

    • Set a low threshold (e.g., CPU > 10%) to trigger a test alert
    • Wait for the condition to occur or force it with a CPU-intensive task
    • Check Notification Center history (click time in menu bar)

  4. Alert-Specific Settings in Overseer:

    • Verify alerts are enabled in Preferences → Alerts
    • Check each alert's threshold and conditions
    • Ensure "Show Notification" is checked for each alert

  5. System-Level Checks:

    • Restart Notification Center: killall NotificationCenter in Terminal
    • Reset notification permissions: Remove Overseer from notification list and re-add
    • Restart Overseer after making changes

Advanced Notification Troubleshooting:

  1. Check Console.app for notification-related errors (search for "Overseer" and "notification")
  2. Test with other apps to ensure Notification Center works system-wide
  3. Safe Mode test: Boot in Safe Mode (hold Shift during startup) to check for software conflicts

Export Issues

Cannot Export Metrics or Reports

Symptoms:

  • Export button does nothing
  • "Permission denied" errors
  • Exported files are empty or corrupted
  • Export process hangs or fails

Step-by-Step Troubleshooting:

  1. Verify File Permissions:

    • Try exporting to Desktop or Documents folder (usually has write access)
    • Check folder permissions: Right-click folder → Get Info → Sharing & Permissions
    • Ensure your user has Read & Write access

  2. Check Disk Space:

    • Ensure sufficient free space for export files
    • Clear temporary files if space is low
    • Check with About This Mac → Storage

  3. Try Different Export Formats:

    • CSV, JSON, and PDF may have different requirements
    • Export smaller time ranges (1 hour vs 24 hours)
    • Try different date ranges to isolate the issue

  4. Application-Specific Checks:

    • Update Overseer to latest version
    • Restart Overseer before exporting
    • Try exporting from a new, simple dashboard

Common Export Scenarios and Solutions:

  • CSV Export Fails: Try different delimiter (comma, semicolon, tab) in Preferences
  • JSON Export Fails: Ensure data doesn't contain invalid JSON characters
  • PDF Export Fails: Check graphics memory, try simpler layouts
  • Large Exports Hang: Export in smaller chunks, increase timeout in Preferences

UI and Display Issues

Symptoms:

  • Interface looks wrong or distorted
  • Metrics don't display properly
  • Graphs not updating
  • High DPI/Retina display issues
  • Theme not applying correctly

Step-by-Step Troubleshooting:

  1. Theme and Appearance Issues:

    • Restart Overseer
    • Check Preferences → Appearance → Theme
    • Match macOS appearance setting (Light/Dark/Auto)
    • Reset appearance: Preferences → Appearance → Reset to Defaults

  2. Missing Dashboard Elements:

    • Reset dashboard layout: Window → Reset Layout
    • Re-add missing metrics from the metrics library
    • Check if monitoring is paused (look for pause button in toolbar)

  3. Graphs Not Updating:

    • Verify real-time monitoring is enabled
    • Check network connectivity if using remote monitoring
    • Restart Overseer and your Mac

  4. High DPI/Retina Display Issues:

    • Update to latest Overseer version
    • Check for graphics driver updates (Apple menu → Software Update)
    • Adjust display scaling in System Settings → Displays

  5. Font or Text Issues:

    • Check macOS font settings in System Settings → Accessibility → Display
    • Adjust text size if needed
    • Reset Overseer preferences (see Advanced section)

Network Monitoring Issues

Symptoms:

  • Network metrics show zero or "No Data"
  • Inaccurate bandwidth measurements
  • Only shows one network interface
  • Network graphs not updating

Step-by-Step Troubleshooting:

  1. Grant Network Permission (see Permission Issues section)

  2. Check Active Network Interface:

    • Overseer monitors the primary active interface
    • Switch between Wi-Fi and Ethernet to see changes
    • Check System Settings → Network for active connections

  3. Restart Network Services:

    • Turn Wi-Fi off/on in menu bar or System Settings
    • Reconnect Ethernet cable
    • Restart Overseer after network changes

  4. Verify macOS Network Stack:

    • Other network monitoring tools may conflict
    • Check Console.app for network-related errors
    • Test with simple network activity (download a file, stream video)

  5. Interface-Specific Issues:

    • VPN connections: May not show in standard monitoring
    • Virtual interfaces: Docker, VMware, Parallels may create virtual interfaces
    • Thunderbolt networking: May require specific permissions

Advanced Network Troubleshooting:

  1. Use Terminal to verify network activity:

    # Check active network interfaces
ifconfig

# Check network usage (install via Homebrew: brew install nload)
nload

  2. Check for firewall restrictions that may block monitoring

  3. Test with different network types (Wi-Fi vs Ethernet vs USB-C)

Battery Monitoring Issues (MacBooks Only)

Symptoms:

  • Battery percentage not showing
  • Battery health metrics missing
  • Power adapter status not detected
  • Cycle count inaccurate

Step-by-Step Troubleshooting:

  1. Verify Hardware Compatibility:

    • Battery metrics only available on MacBooks, MacBook Air, MacBook Pro
    • Desktop Macs (iMac, Mac mini, Mac Studio, Mac Pro) don't have batteries
    • Check your Mac model in About This Mac

  2. Grant Required Permissions:

    • System Monitoring permission is essential
    • Power/battery metrics may require additional IOKit access

  3. Check System Report:

    • Apple menu → About This Mac → System Report → Power
    • Verify battery information appears here
    • If missing here, it's a hardware/macOS issue, not Overseer

  4. Calibrate Battery (for inaccurate readings):

    • Drain battery to <10%, then charge to 100% without using
    • Keep on charger for 2+ hours after reaching 100%
    • macOS will recalibrate battery measurements

Battery-Specific Notes:

  • Cycle Count: Updates slowly (may not change daily)
  • Health Percentage: Calculated by macOS, not real-time
  • Power Source: May take a few seconds to detect adapter changes

Temperature Sensor Issues

Symptoms:

  • Temperature sensors missing
  • Inaccurate temperature readings
  • Only some sensors detected
  • Temperatures not updating

Step-by-Step Troubleshooting:

  1. Hardware Compatibility Check:

    • MacBook Pro: Most sensors available
    • iMac/Mac Studio: Good sensor availability
    • MacBook Air: Limited sensors
    • Older Intel Macs: Varies widely by model

  2. macOS Version Requirements:

    • Full temperature monitoring requires macOS 14.0+
    • Some sensors available on macOS 13.0+
    • Limited sensors on older versions

  3. Grant System Monitoring Permission (essential for temperature data)

  4. Check for Firmware Updates:

    • Apple menu → About This Mac → More Info... → System Settings → General → Software Update
    • Firmware updates can add/enable sensors

  5. Verify with Alternative Tools:

    • Use istats (Homebrew: brew install istats) to check sensor availability
    • Compare with Activity Monitor's Energy tab (for thermal pressure)

Understanding Temperature Readings:

  • CPU/GPU Die: Most accurate, direct sensor
  • Ambient/Case: Less accurate, inferred
  • Different sensors for different components (P-Cores, E-Cores, GPU, SSD)
  • Normal ranges: 40-100°C depending on load and cooling

Advanced Troubleshooting

Resetting Overseer Preferences

If multiple issues persist, reset Overseer to default settings:

  1. Quit Overseer completely (⌘ + Q or Overseer → Quit Overseer)
  2. Remove preference files: 
    rm -rf ~/Library/Preferences/com.overseer.Overseer.plist
rm -rf ~/Library/Application\ Support/Overseer
  3. Remove cache: 
    rm -rf ~/Library/Caches/com.overseer.Overseer
  4. Restart Overseer – it will create fresh preferences
  5. Reconfigure your dashboards and alerts

Checking Console Logs for Errors

  1. Open Console.app from Applications → Utilities
  2. In search, type: process:Overseer or subsystem:com.overseer.Overseer
  3. Look for error (🔴) or warning (🟡) messages
  4. Note timestamps to correlate with issues

Creating Diagnostic Reports

Overseer can generate diagnostic reports:

  1. Go to Help → Create Diagnostic Report
  2. Save the report file
  3. Include this when contacting support for faster resolution

Contacting Support

If you've tried all troubleshooting steps and issues persist:

  1. Gather Information:

    • Overseer version (Overseer → About Overseer)
    • macOS version (Apple menu → About This Mac)
    • Mac model and year
    • Detailed description of the issue
    • Steps you've already tried

  2. Include Diagnostic Data:

    • Console.app logs related to Overseer
    • Diagnostic report from Overseer
    • Screenshots or screen recordings

  3. Contact Methods:

    • Email: support@overseer.com
    • Contact Form: overseer.com/contact
    • Response Time: Typically 24-48 hours on business days

Before Contacting Support, Ensure You Have:

  1. Updated to latest Overseer version
  2. Updated macOS to latest compatible version
  3. Granted all required permissions
  4. Restarted both Overseer and your Mac
  5. Checked Console.app for relevant error messages

For more help, visit our Support Center or check the FAQ for additional answers to common questions.

Back to categoryBack to Documentation

Was this helpful?

Help us improve this documentation by providing feedback.

Report IssueContact SupportEdit this page