Since the Apigee message logging policy does not allow the severity of a message to be specified when using syslog, I would need to drop out of the API Proxy into custom code to do this. The message logging policy is Asynchronous and therefore does not add much (if any) latency to the API flow. I am not sure if a service callout would behave in the same way. My concern here is what is the performance impact if any of adding custom code that the API proxies will have to call out in order to do the logging? The problem will also be compounded by the fact that the logging will be using SSL over TCP. Will there be an added cost in performance of connection setup and tear down for each message?
LinkedIn
Twitter
