Give each source its own panel
Add application files, container streams or remote logs to your workspace. Resize and reorder the panels around the investigation. Keep production labels visible so you always know which environment you are reading.
// Multiple logs / macOS
A Mac log viewer for the whole request.
An error in your API can begin in a worker and surface in your web server. Keep the relevant logs visible together, then follow the same request ID across the panels.
Find your planRead the practical guide ↗YOUR DEBUGGING WORKFLOW
01
api.log02
worker.log03
error.log
lognivoOne workspace. Separate panels.Workflow illustration
// FROM SOURCE TO SIGNAL
A workflow you can return to.
Filter one source. Keep another in context.
Search for a request ID, show selected severity levels and combine text filters. Each panel has its own pause, history and reading-order controls. Expand an entry when the complete message matters.
Return to a useful layout
Save a named view with your panel arrangement. Lock panels that should stay in place or float a log above your editor. Your saved workspace is a layout, not a stored archive of every log entry.
// A CLOSER LOOK
Small controls. More room for the log.
Search, severity filters, reading order and pause stay with their panel. As you resize, secondary actions move into the options menu.
Before you connect.
Does Lognivo merge all files into one timeline?
Sources stay in separate panels. Compare timestamps or search for a shared identifier; Lognivo does not claim automatic distributed tracing or a merged timeline.
Is this a replacement for log storage?
No. It is a desktop viewing workspace with bounded history. Keep retention, collection and always-on monitoring in your existing infrastructure.
Keep the rest of your stack in view.
Make room for the whole story.
macOS 14+ · Apple silicon & Intel
Get Lognivo for Mac