Overview 💥
Sometimes, Liongard Inspectors (for example, your Active Directory Inspector, Windows Server Inspector, or other system inspectors) may fail or produce incomplete data due to caching issues or intermittent errors. Running an inspector in Debug + Clear Cache mode forces a fully fresh inspection, bypassing stored state, and gives you detailed log output for troubleshooting.
Using this mode is especially helpful when:
You're diagnosing failed or stuck inspections.
Inspectors report inconsistent or missing data.
You want to see raw logs to understand where failures occur.
You recently made configuration changes and want to validate them.
Why Use Debug + Clear Cache? 🤔
Cache Reset: Clears existing cached inspection data so that the next run fetches fresh data from the target system.
Verbose Logging: Enables more detailed debug-level logs, helping you trace exactly where in the inspection process something is going wrong.
Accurate Troubleshooting: Helps isolate whether an issue is due to old data, configuration issues, or deeper communication problems.
How to Run Inspectors in Debug + Clear Cache Mode 🧑🏫
Open Liongard Portal
Navigate to Admin → Inspectors.Locate the Inspector
Find the specific inspector you want to run (for example, Microsoft 365, Active Directory, Windows Server, etc.) in the list of configured systems.Run with Debug + Clear Cache
Right click the Play-Pause button.
Select Debug + Clear Cache.
This tells Liongard to clear the inspector's stored cache for that system and run with debug logging enabled.
Wait for Completion
The inspection will run, often taking longer than a standard run due to cache clearing and verbose logging.
Monitor the status until the inspector completes or shows failure.
Reviewing Logs & Results 👀
Once the Debug + Clear Cache inspection has completed:
Click the Folder icon to review the logs. (Note: you can also view and export the logs.)
Look for debug-level log entries, error messages, or stack traces that indicate where the run may have failed or succeeded.
Troubleshooting Common Scenarios 👨💻
Here are some common outcomes and what they may mean:
Problem During Debug + Clear Cache | Possible Cause | Recommended Next Steps |
Inspector still fails | Configuration error, credential issue, or target system problem |
|
Partial data returned | Cache was corrupted; network latency, agent or misconfig. |
|
Run takes unusually long | Very large payload, high object count |
|
Best Practices 😉
Practice | Reasoning / Details |
Use Debug + Clear Cache only when necessary | Standard inspections are faster and less resource-intensive. Reserve debug runs for troubleshooting errors or verifying recent changes. |
Export logs | Logs contain critical information for diagnosing failures. Keep them for your records or when submitting a support ticket. |
Review inspection intervals | Frequent inspections combined with debug mode can overload agents or network resources. Adjust intervals based on environment size and change rate. |
Validate agent connectivity and permissions | Failed inspections often stem from credentials or network/firewall issues. Ensure agents can communicate with target systems and have proper permissions. |
Monitor for recurring issues | If you find yourself repeatedly using debug mode, it may indicate persistent configuration or network issues that need addressing. |
Use off-peak hours for heavy inspections | Scheduling during low-usage periods reduces impact on servers network and agents. |
Document changes and runs | Keep a record of when debug runs are performed, changes made, or errors observed. This helps in root-cause analysis and historical troubleshooting. |
Engage support early for persistent failures | When debug logs show recurring errors, submit them to Liongard Support for deeper analysis. |
When to Contact Liongard Support 🦁
Please reach out to Liongard Support when:
Debug + Clear Cache runs still fail or return errors.
You’re seeing inconsistent data across multiple inspectors.
You want to validate your inspector configuration or review best practices.
When submitting a ticket, include:
The debug logs from your most recent run
Screenshots of error messages or failed runs
The inspector type and system name
Steps to reproduce the problem
Our Support team is happy to help 😇
💬 Start a chat with Leo (Our AI Assistant) or connect with a live support engineer.
📧 Email: support@liongard.com