API catalog shows more quests for a specific API than when 'All' is selected

Updated 6 days ago by Rahul Lahiri

When the 'All' option is selected, we show the count of traces that are available in the catalog. A trace may contain multiple requests, even multiple requests to the same API, depending on how the trace execution.

However, when you select a specific API, the count shows the number of requests for that API in the catalog. If an API is called multiple times from certain requests, then it is possible for the count of a specific API request (requests to a service) to exceed the number of traces in the catalog.


How did we do?