HTTP collection must be enabled on a per-domain basis. Open the Domain module, select a domain, and check the Collect HTTP Data box on the Domain Details page. Repeat for each domain.
HTTP Error Details
Previously, the Developer tab offered few insights for HTTP issues. The Error Details section listed the error’s type, code, message, URL, and the date on which it last appeared. With this update, we’ve added a tab to list the issue’s request and response headers. This tab includes buttons to copy the headers to the clipboard for easy use.
As most DevOps engineers advise against verbose logging on the origin server, engineers often have little to no visibility of the request or response for an API call when debugging an HTTP error. By capturing the headers, Noibu allows an engineer to build a precise case with customer data without turning on verbose logging, a resource-intensive process.
It’s possible for the HTTP Error Details to miss some or all content, depending on what the NoibuJS script could capture and parse. If the tab is missing either the request or response headers, an empty state appears to confirm the information could not be found.
Session Timeline HTTP Events
HTTP information is also visible in the Session Timeline. We’ve added similar insights to HTTP events to give developers more context on what they see in the timeline. Keep in mind that you must check the Show HTTP Events box to see these events.
Not all HTTP entries will have event information. Events with details are purple and clickable, while events without details are grey and non-interactable. Click on a purple entry to expand the event’s details.
This is an early iteration of the feature, and we hope to add even more insights in future releases. We’ve omitted select details–like cookie tracking–from this first iteration. However, as Noibu clients adopt HTTP error details as part of their debugging processes, Noibu will continue adding elements based on what our customers feel is most useful.