Good question, William.  Please see below: Do a web search on the term, “apigee splunk,” and eventually you’ll end up here: https://community.apigee.com/articles/13298/log-messages-into-splunk.html (I’ll refer to this as “the Article.”)  This Apigee Community page is a great place to start for information on configuring Apigee to work with Splunk.  It describes three methods of connecting -using Splunk’s HTTP Event Collector (HEC), using TCP, or using JavaScript.  I’ll cover the first two methods here.  While setting up HEC to work with Apigee is rather straightforward, and I’ll cover this briefly below, the TCP method is a bit trickier and requires some special configuration in Splunk.  Option 1: HEC Utilizing the HTTP Event Collector is by far the easiest method for connecting Apigee to Splunk.  The link for setting up HEC in the Article is no longer available but you can find the Splunk documentation here: https://docs.splunk.com/Documentation/Splunk/8.1.2/Data/UsetheHTTPEventCollector.  Splunk configuration: In summary, the following steps are required to set up an HEC token: On your receiving system (indexer or heavy forwarder), consider creating a new application and index to contain your Apigee config.  I created an app called Apigee along with a corresponding “apigee” index. In the Splunk UI, go to Settings, Data Inputs. Under Local Inputs, select HTTP Event Collector. Click the Global Settings button and select Enable SSL to utilize HTTPS.  Also, make note of the HTTP Port Number.  The default is 8088 but can be changed as required. Click Save. Back on the main HEC page, select New Token Give your token a name (I used “apigee).  Click Next. On the Input Settings page, click Select and select the sourcetype as “_json.” Select an App Context as appropriate. Select an existing index to store the Apigee events – I used the index created above. Click Review, review your settings, then click Submit. Your HEC token will be displayed; make note of it.  You can also get the token from the Data Inputs, HTTP Event Collector page. Apigee configuration: This assumes you have Apigee set up with a working API Proxy. Go to Develop, API Proxies, and select the proxy you’d like to use. Click the Develop tab. Under the Navigator pane, select the “+” next to Policies to add a new policy. A set of policies appears on the left.  Scroll to the bottom of the list and under the Extension section, select the Service Callout policy.  Enter a Display Name for the policy (I used “Splunk_HTTP”), select the HTTP radio button and enter the HTTP Target.  The target will be the publicly accessible IP address and port number for your HEC  - for instance: https:// 198.51.100.1:8088.  Click Add. Under the Code section of the policy, add the following lines (replace the line xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx with your HEC token):   <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ServiceCallout async="false" continueOnError="false" enabled="true" name="Splunk_HTTP"> <DisplayName>Splunk_HTTP</DisplayName> <Properties/> <Request clearPayload="true" variable="myRequest"> <IgnoreUnresolvedVariables>false</IgnoreUnresolvedVariables> <Set> <Headers> <Header name="Authorization">Splunk xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</Header> </Headers> <Payload contentType="application/json" variablePrefix="@" variableSuffix="#"> {"type": "apigee-log","status": "@message.status.code#"} </Payload> <Path>services/collector/raw</Path> <Verb>POST</Verb> </Set> </Request> <Response>calloutResponse</Response> <HTTPTargetConnection> <URL>https://198.51.100.1:8088</URL> </HTTPTargetConnection> </ServiceCallout> ​   Here's a screenshot of the Apigee configuration: Notes: The Payload section is where you can customize what data is being sent to Splunk.  The Article shows a simple message to be sent: {"event":"Logged from EDGE"}.  This can be customized using Apigee Flow Variables.  In my example, I used the “message.status.code” flow variable to return the status code of the event.  More on flow variables may be found here: https://docs.apigee.com/api-platform/reference/variables-reference#request. For the URL, it is possible to change this to use an unsecure HTTP connection instead of HTTPS for testing purposes.  I found this valuable in diagnosing the connection as I could grab a packet capture from my firewall to see how the request was coming in.  If you would like to do this, make sure to uncheck the Enable SSL box in the HEC Global Settings.  Be sure to set it back when your testing is complete! Finally, you need to add this policy to the flow.  For my example, I added the policy to the Proxy Endpoint PostFlow. If all goes well, you should have a working connection.  When I access my API proxy, the following event is sent to Splunk: As you can see, using HEC is pretty straightforward.  Now let’s set up Apigee to use a TCP connection from Apigee to Splunk.  Option 2: TCP: For this configuration, we’ll need to create a receive port in Splunk and add a new API policy in Apigee.  Let’s start with the Splunk configuration. Splunk configuration: On your receiving system (indexer or heavy forwarder), as noted above, consider creating a new application and index to contain your Apigee config.  Add the following to an appropriate inputs.conf file.  This can be in your application or the main file located at $SPLUNK_HOME/etc/system/local:   [tcp-ssl://6514] index = apigee [SSL] serverCert = /opt/splunk/etc/auth/server.pem sslPassword = password ​ Note: The above example utilizes the internal Splunk self-signed certificate, the password of which is simply “password.”  While this may be fine for testing, it is recommended you utilize a signed certificate or a self-signed certificate that you create.  Details on inputs.conf may be found here: https://docs.splunk.com/Documentation/Splunk/latest/Admin/Inputsconf 3. Restart Splunk for the new TCP input to take effect.   Apigee configuration: In your API proxy Go to Develop, API Proxies, and select the proxy you’d like to use. Click the Develop tab. Under the Navigator pane, select the “+” next to Policies to add a new policy. A set of policies appears on the left.  Scroll to the bottom of the list.  This time we’re going to select the Message Logging extension.  Enter a Display Name for the policy (I used “Splunk_TCP”).  This will create a default Message Logging template that we will need to adjust.  Change the <Host> and <Port> sections to suit your config.  The <Message> section can contain any text, including Flow Variables (see example below). Finally, you need to add this policy to the flow.  For my example, I added the policy to the Proxy Endpoint PostFlow. Here’s what the finished config should look like:   Once I access my API, the following event is sent to Splunk: That’s it!  I hope this was helpful for anyone wanting to integrate Apigee with Splunk.         ... View more