You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...so that I can use this for metrics purposes and/or for a better understanding of how to improve my access to the API from a client.
📖 Additional Details
⚖️ Acceptance Criteria
Given a running API and registry with data ingested When I perform a query to the API Then I expect the response to include a took field with the amount of time it takes for the query to be pushed to the registry, parsed by the API service, and then tagged with with the time right before the response is returned by the API service
⚙️ Engineering Details
Similar to ESDIS CMR response, something like:
{
"hits" : 2,
"took" : 11,
"items" : [ {
...
seems like this is tightly coupled with NASA-PDS/pds-api#68 so figured I would add to this sprint as well
The text was updated successfully, but these errors were encountered:
"took" is in what units? If seconds, then float? It is currently number of milliseconds, since most requests are less than a second, and documented as such but could look strange if the did-not-read-the-manual assumption is seconds.
💪 Motivation
...so that I can use this for metrics purposes and/or for a better understanding of how to improve my access to the API from a client.
📖 Additional Details
⚖️ Acceptance Criteria
Given a running API and registry with data ingested
When I perform a query to the API
Then I expect the response to include a
took
field with the amount of time it takes for the query to be pushed to the registry, parsed by the API service, and then tagged with with the time right before the response is returned by the API service⚙️ Engineering Details
Similar to ESDIS CMR response, something like:
seems like this is tightly coupled with NASA-PDS/pds-api#68 so figured I would add to this sprint as well
The text was updated successfully, but these errors were encountered: