We are introducing Message Logging using PostClientFlow. The implementation of PostClientFlow is as follows:
- A shared flow is invoked in PostClientFlow
- The shared flow has 2 policies - first a JS policy to create custom log string, then a MessageLogger policy to log the same to splunk.
1) For the same request sent multiple times, both the policies execute but the flow variables are not populated and do not show up in Trace Tool either. As a result, no log entry is created. We are seeing this behavior even for consecutive 200 OK (successful) requests.
2) Another observation, which is probably by design is that for error flows, whenever a Raise Fault policy is used, flow variables from request or target response are not available. We have never seen a log entry for error scenarios with Raise Fault policy getting executed just before PostClientFlow.
LinkedIn
Twitter
