Find out whether data is empty, partial or unavailable.

Record the build and warnings

lens-top --version
lens --once
lens-health --json | jq '{findings, collection_warnings}'

Zero and unavailable mean different things

Remove filters, run the specialist directly and inspect collection_warnings before concluding that a host has no services, logs, interfaces, listeners or devices. Containers report only their namespace and can legitimately have no service manager, host journal, hardware sensors or mounted certificates.

lens-logs --json | jq '{count: (.logs | length), warnings: .collection_warnings}'
lens-net --json | jq '{interfaces, routes, sockets, warnings: .collection_warnings}'

Narrow slow investigations

Open the specialist instead of waiting for every cockpit domain. External collectors have individual deadlines and interactive views retain the previous frame while new data arrives. On a slow remote connection, use one bounded result:

lens-logs --since "15 minutes ago" --severity error --limit 100 --once
lens-net --filter 443 --once

lens-top --once samples twice and uses a short default measurement window. Passing --interval 2s deliberately requests a two-second sample.

Terminal colours and cleanup

Use --theme light, --theme dark or LENS_THEME when a browser terminal, serial console or multiplexer does not expose its background. Use lens-top --no-color or --ascii when colour or Unicode is unsuitable.

Current builds clear and restore the terminal on normal exit. If a disconnected terminal did not allow cleanup, run reset. Report a normal q or Ctrl+C exit that still leaves content, including the terminal product and dimensions.

Common native-source checks

Use GitHub Issues for support

Open a help issue or bug report. Include build identity, operating system, architecture, command, terminal product and relevant warnings. Remove hostnames, usernames, addresses, logs, SIM identifiers, certificate paths and other private system data first.