Comment by wnederhof

Just to add to that: yes, it actually starts querying once the query has been entered. It basically sends that instruction to the application that has the WireQuery SDK integrated, which, in turn, only sends back data to WireQuery that meets the requirements of the query. Thus, it does not store hundreds of thousands logs in a very large database like most logging tools do. This way, you can deploy the application with _far_ fewer resources - yet, by allowing the end-user to instantiate a session (as well as a WireQuery user), you only capture what is actually relevant to be captured.