github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-23 22:27:21 -04:00
Code Issues Projects Releases Packages Wiki Activity

remove unused links

Browse source 
the links were placeholders to links to the sample configs, but after
a discussion between myself and kurtado, we decided it was fine to
have users copy+paste the configs.
This commit is contained in:
Jordan Sissel 2014-02-14 16:07:54 -08:00
parent c53efb0f44
commit f8d68559ca
1 changed files with 0 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/tutorials/getting-started-with-logstash.asciidoc
View file

@ -177,7 +177,6 @@ For the complete list of (current) configurations, visit the logstash "plugin co
Specifying configurations on the command line using '-e' is only so helpful, and more advanced setups will require more lengthy, long-lived configurations. First, let's create a simple configuration file, and invoke logstash using it. Create a file named "logstash-simple.conf" and save it in the same directory as the logstash flatjar.
http://foo.com[logstash-simple.conf]
----
input { stdin { } }
output {
@ -197,7 +196,6 @@ Et voilà! Logstash will read in the configuration file you just created and run
=== Filters
Filters are an in-line processing mechanism which provide the flexibility to slice and dice your data to fit your needs. Let's see one in action, namely the *grok filter*.
http://foo.com[logstash-filter.conf]
----
input { stdin { } }
@ -254,7 +252,6 @@ The other filter used in this example is the *date* filter. This filter parses o
=== Apache logs (from files)
Now, let's configure something actually *useful*... apache2 access log files! We are going to read the input from a file on the localhost, and use a *conditional* to process the event according to our needs. First, create a file called something like 'logstash-apache.conf' with the following contents (you'll need to change the log's file path to suit your needs):
http://foo.com[logstash-apache.conf]
----
input {
file {
@ -299,7 +296,6 @@ You should be able to see your apache log data in Elasticsearch now! You'll noti
In this configuration, logstash is only watching the apache access_log, but it's easy enough to watch both the access_log and the error_log (actually, any file matching '*log'), by changing one line in the above configuration, like this:
http://foo.com[logstash-apache-wildcard.conf]
----
input {
file {
@ -313,7 +309,6 @@ Also, you might have noticed that logstash did not reprocess the events which we
=== Conditionals
Now we can build on the previous example, where we introduced the concept of a *conditional*. A conditional should be familiar to most logstash users, in the general sense. You may use 'if', 'else if' and 'else' statements, as in many other programming languages. Let's label each event according to which file it appeared in (access_log, error_log and other random files which end with "log").
http://foo.com[logstash-apache-error.conf]
----
input {
file {
@ -350,8 +345,6 @@ OK, now we can move on to another incredibly useful example: *syslog*. Syslog is
First, let's make a simple configuration file for logstash + syslog, called 'logstash-syslog.conf'.
http://foo.com[logstash-syslog.conf]
----
input {
tcp {