Skip to main content

​
Error Analysis

Rockxy automatically detects errors from both network traffic and application logs, groups them by pattern, and correlates errors across sources so you can trace failures from the HTTP layer through to your app’s log output in a single view.
Rockxy error analysis view

​
Entry Points

ActionHow to Access
Errors tabErrors tab in the main sidebar
Error detailClick any error group to expand individual occurrences
Jump to requestClick an occurrence to navigate to the full request in the traffic inspector

​
Error Sources

Rockxy collects errors from three categories:
  • HTTP 4xx/5xx responses — any server response with a status code in the 400–599 range is flagged as an error.
  • Network connection failures — DNS resolution failures, connection timeouts, TLS handshake errors, and other transport-level problems.
  • Log entries at Error or Fault level — application log entries captured by the log engine at the Error or Fault severity level.
Error detection is automatic. Every captured request and log entry is evaluated — there is nothing to configure. Errors appear in the Errors tab as soon as they are detected.

​
Error Grouping

Similar errors are clustered into groups by pattern. The grouping algorithm considers:
  • Endpoint + status code — all 404 responses from /api/v2/users/:id are grouped together, regardless of the specific ID in the path.
  • Error message similarity — log errors with similar message text (ignoring variable parts like timestamps, IDs, and numeric values) are grouped.
  • Connection failure type — transport errors are grouped by failure category (DNS, timeout, TLS, etc.).
Each error group displays:
FieldDescription
PatternA human-readable description of the error pattern
CountTotal number of occurrences in the current session
First SeenTimestamp of the earliest occurrence
Last SeenTimestamp of the most recent occurrence
Sample EntriesA few representative transactions or log entries

​
Error Detail View

Click any error group to expand it and see individual occurrences. Each occurrence shows:
  • The full request URL, method, and status code (for network errors).
  • The complete log message and source metadata (for log errors).
  • A timestamp and duration.
Click any individual occurrence to jump to the full request in the traffic inspector or the full log entry in the Logs tab. The surrounding context (nearby requests, correlated logs) is preserved so you can investigate without losing your place.

​
Cross-Source Correlation

Rockxy links network errors with log errors that share the same context:
  • Same process — the network request and the log entry originate from the same application process.
  • Same time window — the log entry occurred during or immediately after the network request.
When a network error has correlated log entries, the error detail view shows both in a unified timeline. This lets you see, for example, that a 500 response from /api/orders was accompanied by a log error reading “failed to decode order payload: unexpected null in required field.”
Cross-source correlation is where Rockxy differs from traditional proxy tools. Instead of checking Console.app separately, you see the full picture — the HTTP error and the app-side log that explains why — in one place.
Access error analysis from two locations:
  • Errors tab in the main sidebar — shows all error groups for the current session, sorted by most recent occurrence.
  • Analytics > Errors section — the same data in the context of the broader analytics dashboard, alongside performance metrics and trends.
Both views support filtering by:
  • Error source (network, log, or all).
  • Status code range (4xx, 5xx, or specific codes).
  • Time range.
  • Keyword search across error patterns and messages.

​
Next Steps

Performance Insights

Latency percentiles, slow request detection, and payload size tracking.

Log Intelligence

Capture and correlate OSLog streams with network requests.