I want to add message logging in post client flow but not directly rather thru a shared flow for consistency purposes. So I would have this xml:
PC_Flow
PC_Flow is a shared flow with only the message logging step. See attachment.
When I run I see the shared flow step in the trace but not the message logging within the shared flow.
This is on prem not cloud.
Hi @Bill Draven , I havent tried this but as far as I remember from apigee docs, Only MessageLogging policies can be attached to PostClientFlow.
Even if you observe Flow Hooks, there is no concept/way to add SharedFlows to PostClientFlow. So I am assuming we cannot use FlowCallout(Within a proxy level, FlowCallout is again a Policy which executes a SharedFlow) in PostClientFlow.
++ @Dino-at-Google @Anil Sagar @ Google for more info
I need post client which fires after response is sent to client as opposed to the flow hook options which, at best, gives me post-proxy which is before response to client. I will be generate all api proxies and therefore anything I can push to a shared flow benefits me by way of simplifying the build and inevitable maintenance of message logging.. While I was able to add a flow callout in post client and add message logging to the shared flow the message logging never fired.
That said, I will do one of the following:
Inject the same message logging into all apis at build. Not ideal but doable.
Make Message Logging a separate service and call it using one of these approaches:
https://community.apigee.com/articles/2340/asynchronous-http-requests-in-an-api-proxy.html
https://community.apigee.com/questions/58110/asynchronous-calls-using-service-callout-policy.html
@Bill Draven- Did you get this working? I am also trying to see if this is possible.
Thanks,
Santosh
Yes we went with a async callout to a local logging service using this guidance. https://community.apigee.com/questions/58110/asynchronous-calls-using-service-callout-policy.html
