The command line waits, cursor blinking, while packets rush across the network you cannot see. You type lnav, and a wall of logs forms in front of you, clean, colored, and searchable. But the data you need lives behind Zscaler, filtered and encrypted, and the clock is running.
Lnav is a powerful, terminal-based log viewer. It reads from local files, streams from stdin, and indexes everything for instant search. With SQL queries built in, you can sort, filter, and pivot data without leaving your shell. When systems span hybrid clouds and private networks, Lnav gives you speed and context on demand.
Zscaler acts as a secure gateway, inspecting and controlling network traffic. For engineers who need to work with logs from systems and services routed through the Zscaler cloud, a gap appears: how do you feed Lnav with relevant log data that lives beyond your immediate network reach?
The solution begins with authenticated, authorized access to the sources behind Zscaler. This often means configuring your client or agent to resolve endpoints through Zscaler’s tunnels while still outputting raw logs to a local store or stream. Scripts or lightweight collectors can tail these sources, push them through STDOUT, and pipe them directly into Lnav: