Overview 💥
Inspector logs provide critical visibility into what happened during your last inspection. By reviewing these logs, you can diagnose failures, verify data pulls, and understand exactly which steps executed and whether any errors occurred.
Liongard makes it easy to access, review, and export logs from your inspectors so you can troubleshoot effectively or provide detailed context when opening support tickets.
Why Review Inspector Logs? 🤔
Troubleshooting failures: If an inspection fails or returns unexpected data, logs can show you error messages, stack traces, or authentication problems.
Understanding behavior: Logs help you see whether your configuration (e.g., credentials, query scope) is working as expected.
Audit and compliance: When you need to justify inspection activity or demonstrate data collection, logs provide proof of what ran and when.
Support diagnostics: If you open a ticket, logs are often the first thing Support will ask for — having them ready speeds up resolution.
How to Access Inspector Logs (Step-by-Step) 👨💻
Go to the Liongard Portal
Navigate to Admin → Inspectors in the Liongard dashboard.Select the Target Inspector / Launchpoint
Locate the specific Inspector for which you want to view logs.Open Logs
Click the Folder icon to review the logs.
Review the Logs
The log window displays data from the last inspection only.
Look for entries such as “starting inspection”, “error encountered”, or “inspection completed successfully”.
Pay close attention to error codes, warnings, and timestamps.
Export Logs
You can export the logs to Excel directly from that window. =
Exported logs make it easier to share with your team or with Liongard Support when raising a ticket.
Important Behavior: What Liongard Stores 🚀
1️⃣ Inspector Logs Only Show the Most Recent Inspection
Inspector logs are not long-term log repositories.
They display only the latest run’s logs for each inspector.
2️⃣ Historical Inspection Data IS Stored — via Timelines
While the Inspector Log page shows only the latest run, Liongard maintains broader historical data through "Timelines". Liongard retains up to 7 days of inspection history.
3️⃣ After 7 Days
Older inspection logs are automatically archived and no longer visible in the UI.
Best Practices for Using Inspector Logs 🧑🏫
Practice | Why It Matters |
Export logs regularly | Keeps a historical record of inspection behavior and helps track recurring errors. |
Annotate when issues occur | If you see an error, note the date, what you changed, or what other events happened in the environment. This helps with root-cause analysis. |
Correlate with inspector schedule | Align log timestamps with your inspection schedule to understand when issues are likely to happen. |
Gather logs before contacting Support | Log entries are often the fastest way for Support teams to diagnose and fix a problem. Have them ready when you file a ticket. |
Limit access to logs | Only trusted administrators should view or export logs, since they may contain sensitive information. |
Common Log Messages & What They Mean 😉
Here are a few common log entries you may see — and how to interpret them:
Log Entry | Meaning / Troubleshooting Tip |
| Agent couldn’t validate credentials. Verify username/password or token. |
| The target system may be slow to respond. Consider increasing timeout or checking network latency. |
| The Inspector couldn’t reach the target. Confirm network, firewall, or agent connectivity. |
| Something in the data parsing or schema changed. Review config or report to Support. |
| The run finished successfully. No action needed — unless data missing. |
When to Contact Liongard Support 🦁
You should reach out to Support when:
Logs show persistent or unexplained errors.
Inspections fail repeatedly after configuration changes.
You can reproduce an error, but don’t know how to fix it.
You want help interpreting specific log entries or structured data.
What to Include in Your Support Request:
Exported log file (Excel).
Name of the Inspector or launchpoint in question.
Timestamp of the failure / relevant log entries.
Description of recent changes in settings, credentials, or environment.