The token is not part of the standard syslog interface, and so there is no explicit element in the Syslog configuration for including that token .
According to my reading of the sumologic documentation, you need to embed the token into the message itself. For example, supposing you have the token ABCDEFG12345 , then you might use this configuration:
You could of course, parameterize the token as well. If you populate the token from a KVM or some other AssignVariable policy, and use the variable name “sumologic.token” , then you could use this alternative policy configuration:
It is working after adding the below snippet. One question, when i see the log in sumo, it actual log is getting appended with “<14>1 2018-02-27T21:31:05.005+0000 19ea1fc2-e676-418b-b8e1-848da00a2732 Apigee-Edge - - -”. Do you know how can i get rid of this?
I reviewed my notes on this, and have found a known issue concerning message logging. b/68722102 - MessageLogging FormatMessage False Not Working
Per this known issue, the expectation is that with FormatMessage set to “false”, only the message part of the syslog, and exclude:
the syslog priority score <14>,
extra date timestamp,
syslog token
Currently the way that FormatMessage set to “false” works, only the syslog token is excluded.
We are using sumologic free acccount. How can i test message logging policy. I am able to log error messages from shared flow using the JS approach suggested at https://community.apigee.com/articles/32286/logging-to-sumo-logic-using-javascript-and-http.html. But for asynchronous and postclient flow i need to test with free account especially success responses. Is it possible. thanks