Few questions in integrating api proxy with splunk for logging purpose
We want to log from our proxy into our Splunk instance. The Splunk instance will be guarded by a API key for authorization. We would like to log from postFlow postClientFlow to ensure that we do not introduce additional latency. The only policy allowed in postClientFlow is MessageLoggingPolicy which unlike a serviceCallOut, only allows a TCP based connection into Splunk where I do not see a place to specify auth info.
Questions:
1. Is there any way we can specify auth in MessageLoggingPolicy?
2. Is there any way apigee can be configured to allow for serviceCallOut policy in postClientFlow?
3. Any other mechanism that you can think of to log into a remote splunk instance that requires auth without introducing additional latency?
Best Answer
Answer by Alex Koo
·
Mar 29, 2016 at 11:34 PM
Also, you may want to check out this community post depending on what protocol you wish to use:
https://community.apigee.com/articles/13298/log-messages-into-splunk.html
You can make an asynchronous web request using a javascript policy. This would introduce minimal latency. Some links: http://docs.apigee.com/api-services/content/httpclient-javascript-object
and https://community.apigee.com/articles/2340/asynchronous-http-requests-in-an-api-proxy.html
