Issue in Trace Tool with Apigee 4.50.00

Hello Community, We are seeing an issue after we upgraded to Apigee 4.50.00

If you have a service-callout as first policy to execute on a conditional flow,

The shared flow present on Pre-Flow would not display all the policies on the trace.

If you remove the service-call call from conditional flow, everything on trace looks good.

Please let me know if anyone as seen this or replicate it ?

0 7 295
7 REPLIES 7

Not applicable

it's interesting.

Can you attach your shared flow xml and proxyendpoint xml?

Hello @Ajitav

Attaching here is the test shared flow and the proxy. Please do share if you see anything different.

This issue we see is only for Apigee 4.50.00

Thanks

Sid

shared-flow-problem-rev2-2020-08-12.zip
policy-check-rev4-2020-08-12.zip

not able to download.

Yep me too. Anyways I had mentioned the steps

Steps

1. Create a no target proxy

2. attach a SC policy in a preflow (say target http://google.com)

3. attach any other policy after that (Ex: spike arrest)

4. create a conditional flow (GET or any other)

5. attach second SC policy to the conditional flow. (target http://google.com)

6. Save and deploy.

7. Fire a GET request from a rest client for that conditional flow.

8. observer the trace (as spike arrest will not be shown, and only two SC policies will be displayed back to back)

I believe the problem is more with the service call out rather than shared flow.

Steps

1. Create a no target proxy

2. attach a SC policy in a preflow (say target http://google.com)

3. attach any other policy after that (Ex: spike arrest)

4. create a conditional flow (GET or any other)

5. attach second SC policy to the conditional flow. (target http://google.com)

6. Save and deploy.

7. Fire a GET request from a rest client for that conditional flow.

8. observer the trace (as spike arrest will not be shown, and only two SC policies will be displayed back to back)

Edit : Policies between two service calls-outs are not displayed on trace with this version of Apigee. @Dino-at-google can you validate our findings ?

Ben confirmed the findings : https://community.apigee.com/questions/86287/apigee-bug-45000.html

Closing this thread.