Search and filter request log records

Search and filter request log records


Recently, after a few months of work, we have completed another cool feature that allows Expert mockers to search and filter request log records. Yes, probably you’ve guessed already that this is a premium subscription plan feature, because it does require extra resources and therefore we cannot provide it to everyone at the moment, though we do plan this in future.

Every mocker who owns an Expert subscription is able to filter log records by HTTP method(s), HTTP status code(s), URL Path (URI), date and finally by request or response text. As you might know already, each expert plan can contain up to 50000 records in the log and filtering/searching request records from the past might be crucial for many developers.

So, let’s review more specifically each filter. First of all, you may select one or multiple HTTP methods. The HTTP status code(s)  filter behaves similarly. But because HTTP protocol provides so many codes, in addition to them, we’ve decided to provide wildcard representation of each status code type, e.g. 20x, 30x, 40x and 50x. For example, selecting 20x will filter records with any success status code like 200, 201, 202 and so forth.

URL path or URI filter allows partial matches. As for the date/time filters. You do not have to provide full date/time (e.g. 2021-03-29 00:00:00), instead you may simply use 2021-03-29 which will be converted to 2021-03-29 00:00:00 by our filter engine.

Finally, you may search by any keyword from the request or response including their headers and bodies. For your information, we index keywords with minimum 3 characters and maximum 32. So, queries like “it” or “no”  will not narrow down the log records, but the word “yes” can definitely help you with this task.

Happy API mocking!