Log Intelligence
Rockxy captures application logs alongside network traffic and correlates them by timestamp and process. When a network request fails, you see the log output that happened at the same time from the same app — no more switching between Console.app and your proxy tool.
Entry Points
| Action | How to Access |
|---|---|
| Logs tab | Logs tab in the main sidebar |
| Log settings | Settings > Logs |
| Correlated logs for a request | Select a request > Logs tab in the inspector |
| Jump to correlated request | Select a log entry > Jump to Request |
Log Sources
OSLog
System and application logs captured via OSLogStore (macOS 12+). Filter by subsystem, category, and process to focus on your app’s output.
Process stdout/stderr
Capture standard output and standard error from child processes via Process pipe. Useful for CLI tools and scripts that log to the terminal.
Custom Sources
Extend log capture via the plugin protocol. Add sources for syslog, file tailing, remote log streams, or any other log format your workflow requires.
Capturing Logs
Enable log capture from the toolbar toggle or in Settings > Logs. Once enabled, Rockxy streams logs in real time from all configured sources. To reduce noise, filter by specific apps or subsystems:- Click the Filter button in the Logs toolbar.
- Select the target application, subsystem, or category.
- Only matching log entries appear in the list.
Log Levels
| Level | Description | Color |
|---|---|---|
| Debug | Verbose debugging output, typically disabled in release builds | Gray |
| Info | Informational messages about normal operation | Blue |
| Notice | Notable conditions that are not errors | Cyan |
| Warning | Potential issues that may require attention | Orange |
| Error | Error conditions that caused a failure | Red |
| Fault | Critical system-level failures | Purple |
Log-Request Correlation
Rockxy automatically correlates log entries with network requests using two signals:- Timestamp proximity — log entries that occurred within the duration of a network request are candidates for correlation.
- Process matching — the log entry’s process identifier must match the app that originated the network request.
Correlation accuracy depends on timestamp precision and correct process attribution. OSLog entries have microsecond timestamps, so correlation is typically accurate to within a few milliseconds. Process stdout/stderr logs may have slightly lower precision depending on the buffering behavior of the target process.
Log Buffer
Rockxy holds up to 100,000 log entries in an in-memory ring buffer for fast access and filtering. When the buffer reaches capacity, the oldest entries are moved to SQLite storage. Persisted log entries remain searchable and accessible from the Logs tab — they load on demand when you scroll past the in-memory boundary or search for older entries. Buffer size is configurable in Settings > Logs > Buffer Size.Log Filtering
Filter the log list using any combination of:- Level — show only entries at or above a minimum severity level.
- Source — OSLog, stdout/stderr, or custom plugin sources.
- Keyword — free-text search across the log message content.
- Time Range — restrict to entries within a specific time window.
- Process — filter by process name or PID.
Next Steps
Error Analysis
Automatic error detection and pattern grouping across network and logs.
Performance Insights
Latency percentiles, slow request detection, and payload tracking.
Traffic Capture
How Rockxy captures HTTP, HTTPS, and WebSocket traffic.