Roberto Navas suggested an idea · Oct 17, 2016 at 10:49 PM · 188 Views tracefiltering
Currently, the Trace tool allows to Filter requests by HTTP Request Headers or Query Parameters.
However, in REST APIs, usually the main *identifier* of the request you want to trace if usually found in the URI Path and HTTP Verb.
for example:
Tracing traffic for a specific User usually involves filtering by URI Path:
GET /users/user1234
Tracing traffic for a specific Resource also involves filtering by URI Path and HTTP Verb:
POST /transactions GET /transactions/* GET /users/john/transactions/* GET /users/john/friends/* GET /users/john/**
Having this type of Filters in the Trace tool will make it inmensely more useful for any API Proxy with traffic, eliminating the need to do massive Traces and lot of post analysis
Help us make things better. Share your great idea or vote for other people's.