[wnederhof]

WireQuery uses rrweb for capturing the frontend interactions. However, perhaps I can answer a similar question, which is how it compares to other offerings.

The main difference between existing tools and WireQuery is that WireQuery was designed for capturing the interactions within the complete stack. This manifests itself in the following ways:

- The frontend recording is paired with the network calls on the backend, which can consist of the entire trace (i.e. the data of system A calling system B, system B calling system C, etc.), including the actual request and response bodies, headers, etc; - There is an exploration and query-in-the-background feature. These features allow you to run arbitrary queries against a backend system that will capture any network request that meets your criteria, optionally paired with the complete trace and some transformations. For instance, this can be helpful when you want to know what the API calls were with their payloads when a system in the middle of your landscape retuns a status code of 500. - The SDKs contain masking facilities to ensure that sensitive data is scrubbed. For instance, using Java, you can simply use @Masked on a field to have the sensitive data removed. Similar offerings often require you to do that manually.

[codethief]

Thanks for elaborating!