Skip to content

Filter Transaction list based on Request Body contents #847

@ArjanSM

Description

@ArjanSM

⚠️ Is your feature request related to a problem? Please describe

We are using Chucker to inspect our https requests & responses and that also includes GraphQL.
But due to the diverse and numerous modules in our application making network requests, the transaction list can sometimes become huge. Filtering on the basis of the URL doesn't help because the endpoints for all the GraphQL requests are just the same(because all our GraphQL requests are POST requests).
Filtering the transaction list on the basis of the request body content would be extremely helpful to filter specific transactions not limited to just GraphQL.

💡 Describe the solution you'd like

A very naive solution, without requiring any UI change, would be to update the SQL query in the HttpTransactionDao's getFilteredTuples() function to search the user entered text in the request body as well. Eventually updating the query to:-

 "SELECT id, requestDate, tookMs, protocol, method, host, " +
            "path, scheme, responseCode, requestPayloadSize, responsePayloadSize, error, isGraphQLRequest FROM " +
            "transactions WHERE responseCode LIKE :codeQuery AND (path LIKE :query " +
            " OR requestBody LIKE :query) ORDER BY requestDate DESC"

📊 Describe alternatives you've considered

Nothing so far.

📄 Additional context

chucker_filter_based_request_body

🙋 Do you want to develop this feature yourself?

  • Yes
  • No

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions