Hello Team,
@Anil Sagar @ Google @sarthak @gbhandari @Dino @Harry Reynoso @Sai Saran Vaidyanathan @Gowdhaman Tamilarasan
Just to move forward with the logs we have to consider apigee log message using Splunk, below are my question that will help us to move forward with development.
- What is MessageLoggingPolicy structure look like, if below one can we used then its fine, apart from this please let me know?
<MessageLogging name="LogToSyslog">
<Syslog>
<Message>[3f509b58 tag="{organization.name}.{apiproxy.name}.{environment.name}"] Wea ther request for WOEID {request.queryparam.w}.</Message>
<Host>logs-01.splunk.com</Host>
<Port>514</Port>
<Protocol>TCP</Protocol>
<FormatMessage>true</FormatMessage>
</Syslog>
<logLevel>ALERT</logLevel>
</MessageLogging>
- How to form message payload for MessageLogging, I found below two, which one can we use..?
A.
<Message>[3f509b58 tag="{organization.name}.{apiproxy.name}.{environment.name}"] Weather request for WOEID {request.queryparam.w}.</Message>
B.
<Message> Logging time = {system.time} | Timestamp = {system.timestamp} | Log Level = {logging.loglevel} | Environment = {environment.name} | API = {apiproxy.name} | ClientID = {client_id} | App = {developer.app.name} | Data = {logging.data}
</Message>
- Can we use a shared flow structure?
If no, please let us know the reason
- Can we force to disable this log policy?
We required this to do on a temporary basis once in production then will remove this element/tag