SysLog in MessageLogging Policy

[NikhilAnand_whp]

Hello,

I am trying to set up an ELK stack for message logging from APIGEE X. I am using ML policy, but the message doesn't reach log stash server. How do i check, if the connectivity exists between APIGEE X and destination syslog server (log stash in my case). As this is async method of logging, the proxy always succeeds irrespective of what syslog server ip i use. So where do I see, if there are any errors in APIGEE X while sending the logs over to syslog server ?

@dchiesa1 

[amitkhosla]

Not sure if it helps, but if you are using policy in post client flow (which is recommended), the proxy will always pass irrespective it could log or not.

Also, as per my limited understanding, default logging pushes logs to cloud logging. Did you make some configuration to let it publish to logstash?

[NikhilAnand_whp]

Yes, the recommendation is to use in post client flow, but even if we use this anywhere else, proxy will execute successfully irrespective of the actual logging.

ML Policy give two feature, either to log in cloud logging or push it to a sys log server. I am using the syslog server option.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<MessageLogging continueOnError="false" enabled="true" name="ML-LogStash">

  <DisplayName>ML-LogStash</DisplayName>

  <Syslog>

    <Message>Message.id = {request.header.id}</Message>

    <Host>10.51.10.41</Host>

    <Port>2000</Port>

  </Syslog>

</MessageLogging>

Irrespective of what ip/port, i use, it is always successful, so where do I see the failure message, saying APIGEE wasn't able to connect to the target server as the server is unreachable  ?