Troubleshooting
Most questions about the data come down to four things: the inventory, the scan, your scope and your filters. Check them in that order.
The numbers look too old
- Open the Assets page and look at Collected. An inventory is sent on a schedule, and after a package change on Linux hosts. A host that has not reported for a long time is listed with an old date.
- Look at Scan pending. A new inventory is scanned shortly after it arrives. A pending asset still shows the findings of its previous inventory.
- On the dashboard, check Last scan and Agents online. If the last scan is old or agents are offline, ask an administrator to check the server and the agents.
A host, cluster or namespace is missing
Your scope decides what you see. If the host or cluster you need is not listed, you may not be allowed to see it. Ask an administrator to check your scope on the Settings page.
Also check the filters: a filter in the bar, or a value in the address of the page, hides everything else. Clear filters shows the unfiltered view.
A page or a button is missing
Pages and buttons depend on your roles. Dependencies, Findings and Assets need the inventory permission; Agents, Reports, Scans, Alerts and CPE mappings each need their own. If a page you need is missing, your administrator can add the role that grants it. The permissions list shows what each one covers.
An export or a report has fewer rows than expected
The server limits exports and reports to a number of rows, 10,000 by default. A report that stops short should be split with a narrower filter. Filters also apply to exports: the export of a filtered page holds only the filtered rows.
A report failed
Open the report row to read the error. Common causes are a filter that matches nothing, or a report that is too large to render in time. Narrow the filter and use Recreate. If the error persists, give the message to your administrator.
A finding has no fix
No fix yet means no fixed version is known. Check the vulnerability at its source, in a new tab from the vulnerability identifier, for mitigations. Won't fix means the upstream project decided not to fix it, which may still need a compensating control.
Getting help
Send your administrator the page address, which contains your filters, and the time you saw the problem. That is usually enough to find the cause in the logs.