Fluent::Plugin::SplunkHTTPEventcollector, a plugin for Fluentd
Splunk output plugin for Fluent event collector.
This plugin interfaces with the Splunk HTTP Event Collector: http://dev.splunk.com/view/event-collector/SP-CAAAE6M
<match **>
type splunk-http-eventcollector
server 127.0.0.1:8088
verify false
token YOUR-TOKEN
# Convert fluent tags to Splunk sources.
# If you set an index, "check_index false" is required.
host YOUR-HOSTNAME
index SOME-INDEX
check_index false
source {TAG}
sourcetype fluent
# TIMESTAMP: key1="value1" key2="value2" ...
time_format unixtime
format kvp
# Memory buffer with a short flush internal.
buffer_type memory
buffer_queue_limit 16
buffer_chunk_limit 8m
flush_interval 2s
</match>
Add this line to your application's Gemfile:
gem 'fluent-plugin-splunk-http-eventcollector'
And then execute:
$ bundle
Or install it yourself as:
$ gem install fluent-plugin-splunk-http-eventcollector
Whatever is appropriate for your environment. Note: If you're using the
td-agent
package, it brings with it its own "embedded" Ruby environment with
either td-agent-gem
or /opt/td-agent/embedded/bin/gem
depending on platform.
Put the following lines to your fluent.conf:
<match **>
type splunk-http-eventcollector
# server: Splunk server host and port
# default: localhost:8088
server localhost:8088
# protocol: Connect to Splunk server via 'http' or 'https'
# default: https
#protocol http
# verify: SSL server verification
# default: true
#verify false
# token: the token issued
token YOUR-TOKEN
# proxy: The URI of a proxy server to use, or the string "env"
# to use the values set in the environment.
# default: <none>
#proxy http://myuser:somepassword@192.0.2.1:8080
#
# Event Parameters
#
# host: 'host' parameter passed to Splunk
host YOUR-HOSTNAME
# index: 'index' parameter passed to Splunk (REST only)
# default: <none>
#index main
# check_index: 'check-index' parameter passed to Splunk (REST only)
# default: <none>
#check_index false
# host: 'source' parameter passed to Splunk
# default: {TAG}
#
# "{TAG}" will be replaced by fluent tags at runtime
source {TAG}
# sourcetype: 'sourcetype' parameter passed to Splunk
# default: fluent
sourcetype fluent
#
# Formatting Parameters
#
# time_format: the time format of each event
# value: none, unixtime, localtime, or any time format string
# default: localtime
time_format localtime
# format: the text format of each event
# value: json, kvp, or text
# default: json
#
# input = {"x":1, "y":"xyz", "message":"Hello, world!"}
#
# 'json' is JSON encoding:
# {"x":1,"y":"xyz","message":"Hello, world!"}
#
# 'kvp' is "key=value" pairs, which is automatically detected as fields by Splunk:
# x="1" y="xyz" message="Hello, world!"
#
# 'text' outputs the value of "message" as is, with "key=value" pairs for others:
# [x="1" y="xyz"] Hello, world!
format json
#
# Buffering Parameters
#
# Standard parameters for buffering. See documentation for details:
# http://docs.fluentd.org/articles/buffer-plugin-overview
buffer_type memory
buffer_queue_limit 16
# buffer_chunk_limit: The maxium size of POST data in a single API call.
#
# This value should be reasonablly small since the current implementation
# of out_splunk-http-eventcollector converts a chunk to POST data on memory before API calls.
# The default value should be good enough.
buffer_chunk_limit 8m
# flush_interval: The interval of API requests.
#
# Make sure that this value is sufficiently large to make successive API calls.
# Note that a different 'source' creates a different API POST, each of which may
# take two or more seconds. If you include "{TAG}" in the source parameter and
# this 'match' section recieves many tags, a single flush may take long time.
# (Run fluentd with -v to see verbose logs.)
flush_interval 60s
</match>
# Input from applications
<source>
type forward
</source>
# Input from log files
<source>
type tail
path /var/log/apache2/ssl_access.log
tag ssl_access.log
format /(?<message>.*)/
pos_file /var/log/td-agent/ssl_access.log.pos
</source>
# fluent logs in text format
<match fluent.*>
type splunk-http-eventcollector
protocol rest
server splunk.example.com:8089
auth admin:pass
sourcetype fluentd
format text
</match>
# log files in text format without timestamp
<match *.log>
type splunk-http-eventcollector
protocol rest
server splunk.example.com:8089
auth admin:pass
sourcetype log
time_format none
format text
</match>
# application logs in kvp format
<match app.**>
type splunk-http-eventcollector
protocol rest
server splunk.example.com:8089
auth admin:pass
sourcetype app
format kvp
</match>
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request