First of: Thank you for your work. Really appreciate it!
I have been trying to integrate api-analytics into my project and have found that it handles query params a bit differently than I expected it to.
I have an API endpoint that looks like this GET /uploadplan?date=yyyy-mm-dd. Since a HTTP body is not expected for GET requests I chose this approach. However, I have found that the grouping in the dashboard does not expect multiple requests on the same endpoint with different query parameters.
I do understand that there are multiple viewpoints on this topic. My suggestion would be to either
- disregard query parameters when grouping requests on the dashboard
- add a toggle button on the dashboard that allows the user to choose whether or not to ignore the query params
If this is something you want to address, I would be happy to contribute a solution myself. I have pinpointed the issue to this endpointID which seems to be the identifier for grouping multiple requests.

First of: Thank you for your work. Really appreciate it!
I have been trying to integrate api-analytics into my project and have found that it handles query params a bit differently than I expected it to.
I have an API endpoint that looks like this
GET /uploadplan?date=yyyy-mm-dd. Since a HTTP body is not expected for GET requests I chose this approach. However, I have found that the grouping in the dashboard does not expect multiple requests on the same endpoint with different query parameters.I do understand that there are multiple viewpoints on this topic. My suggestion would be to either
If this is something you want to address, I would be happy to contribute a solution myself. I have pinpointed the issue to this
endpointIDwhich seems to be the identifier for grouping multiple requests.