Hi All,
Apigee Trace is very useful when we try using filters in it.
We have tried using Predefined UI Filters for Response Codes, Headers, QueryParams, Path, Response Time Greater Than and Custom filters.
As per the document: https://cloud.google.com/apigee/docs/api-platform/debug/trace ,
Few observations from our test results, PFB:
1)The response code is expected to be given in response.status.code == value, for example: response.status.code == 401.
It was observed that, it works for 200,400 HTTP status codes, but also expected to work for 401,405 and other status codes.
2)In some scenario's, the filters got useful and received the expected response but whenever tried to set for path,
didn't found any scenario working for it and didn't got any response. Is there any scenario defined for path as well, in filters?
3)For Response Time Greater Than, it is expected to be
target.duration > _value_ and client.duration > _value_
But, even when tried with Less Than, for example target.duration < 900 and client.duration < 900,
it also works in Response Time Greater Than. Is it expected to be like this?
4)Another Scenario in Response Code, tried with response.status.code > '200' which gives response for 200,400 status codes,
Is this expected to give response for greater than '200' status codes?
Please share your inputs on these observations.
Thank You!
@kurtkanaskie@dchiesa1@Sai Saran Vaidyanathan
@dknezic@ganadurai@Harish123@Manisha_Chennu@Peeyush_Singhai@markjkelly @shrenikkumar-s
LinkedIn
Twitter
