mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 06:37:19 -04:00
- more docs!
This commit is contained in:
parent
6583909df1
commit
b01595ad47
5 changed files with 16 additions and 4 deletions
|
@ -1,6 +1,11 @@
|
|||
require "logstash/outputs/base"
|
||||
require "logstash/namespace"
|
||||
|
||||
# Push events to an AMQP exchange.
|
||||
#
|
||||
# AMQP is a messaging system. It requires you to run an AMQP server or 'broker'
|
||||
# Examples of AMQP servers are [RabbitMQ](http://www.rabbitmq.com/) and
|
||||
# [QPid](http://qpid.apache.org/)
|
||||
class LogStash::Outputs::Amqp < LogStash::Outputs::Base
|
||||
MQTYPES = [ "fanout", "direct", "topic" ]
|
||||
|
||||
|
|
|
@ -11,7 +11,6 @@ require "logstash/outputs/base"
|
|||
# You can learn more about elasticseasrch at <http://elasticsearch.org>
|
||||
class LogStash::Outputs::Elasticsearch < LogStash::Outputs::Base
|
||||
|
||||
# http://host/index/type
|
||||
config_name "elasticsearch"
|
||||
|
||||
# ElasticSearch server name. This is optional if your server is discoverable.
|
||||
|
|
|
@ -4,7 +4,7 @@ require "logstash/outputs/base"
|
|||
# GELF output. This is most useful if you want to use logstash
|
||||
# to output events to graylog2.
|
||||
#
|
||||
# http://www.graylog2.org/about/gelf
|
||||
# More information at <http://www.graylog2.org/about/gelf>
|
||||
class LogStash::Outputs::Gelf < LogStash::Outputs::Base
|
||||
|
||||
config_name "gelf"
|
||||
|
|
|
@ -1,6 +1,8 @@
|
|||
require "logstash/namespace"
|
||||
require "logstash/outputs/base"
|
||||
|
||||
# This output is only used for internal logstash testing and
|
||||
# is not useful for general deployment.
|
||||
class LogStash::Outputs::Internal < LogStash::Outputs::Base
|
||||
config_name "internal"
|
||||
|
||||
|
|
|
@ -5,19 +5,25 @@ require "uri"
|
|||
# TODO(sissel): Move to something that performs better than net/http
|
||||
require "net/http"
|
||||
|
||||
# Got a loggly account? Use logstash to ship logs to Loggly!
|
||||
#
|
||||
# This is most useful so you can use logstash to parse and structure
|
||||
# your logs and ship structured, json events to your account at Loggly.
|
||||
#
|
||||
# To use this, you'll need to use a Loggly input with type 'http'
|
||||
# and 'json logging' enabled.
|
||||
class LogStash::Outputs::Loggly < LogStash::Outputs::Base
|
||||
config_name "loggly"
|
||||
|
||||
# The hostname to send logs to. This should target the loggly http input
|
||||
# server which is usually "logs.loggly.com"
|
||||
#config :url, :validate => :string, :default => "https://logs.loggly.com/"
|
||||
config :host, :validate => :string, :default => "logs.loggly.com"
|
||||
|
||||
# The loggly http input key to send to.
|
||||
# This is usually visible in the Loggly 'Inputs' page as something like this
|
||||
# https://logs.hoover.loggly.net/inputs/abcdef12-3456-7890-abcd-ef0123456789
|
||||
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
# ^ key ^
|
||||
# \----------> key <-------------/
|
||||
#
|
||||
config :key, :validate => :string, :required => true
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue