![]() Sourcetype = axway:apigateway:traffic:json If the data is ingested via HTTP Event Collector, you need to configure an HEC input: Open logging data should be indexed under the sourcetype 'axway:apigateway:traffic:json' Index Axway API Gateway open logging data Install the Add-on on your Splunk platform.įor distributed environments, the Add-on needs to be deployed on the Search Head as well as on Indexer(s) or Heavy Forwarder depending on the ingress instance as it includes parsing configuration parameters. monitoring open logging directory with Splunk Universal Forwarder). This Add-on should however work with more simple architectures and ingestion methods depending on your constraints (i.e. In our AWS setup, open logging data - group-2_instance-1_traffic.log - is monitored by a CloudWatch agent and pulled to a CloudWatch Log Group then pushed to Splunk HTTP Event Collector via Kinesis Firehose. Please refer to the following documentation: Traffic logs are JSON structured data which schema is documented here: Collect Axway API Gateway data from your Gateway It is meant to be used with the Axway API Gateway App for Splunk. Axway API Gateway Add-on for Splunk provides lightweight field extractions for your Axway API Gateway data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |