Skip to content

Commit

Permalink
- don't reference "?local" anymore since it's obsolete
Browse files Browse the repository at this point in the history
  • Loading branch information
jordansissel committed Jan 17, 2013
1 parent 080ae5e commit 81e6952
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions docs/tutorials/10-minute-walkthrough/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ The same config as step 3 is used.

### Run it:

java -jar logstash-%VERSION%-monolithic.jar agent -f hello-search.conf -- web --backend 'elasticsearch:///?local'
java -jar logstash-%VERSION%-monolithic.jar agent -f hello-search.conf -- web --backend 'elasticsearch://localhost/'

The above runs both the agent and the logstash web interface in the same
process. Useful for simple deploys.
Expand Down Expand Up @@ -100,7 +100,7 @@ Same as the previous step, but we'll output to ElasticSearch now.

### Run it

java -jar logstash-%VERSION%-monolithic.jar agent -f apache-elasticsearch.conf -- web --backend 'elasticsearch:///?local'
java -jar logstash-%VERSION%-monolithic.jar agent -f apache-elasticsearch.conf -- web --backend 'elasticsearch://localhost/'

Logstash should be all set for you now. Start feeding it logs:

Expand Down
4 changes: 2 additions & 2 deletions docs/tutorials/getting-started-simple.md
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ Obviously this is fairly useless this way. Let's add the final step and test wit
We've already proven that events can make it into Elasticsearch. However using curl for everything is less than ideal.
Logstash ships with a built-in web interface. It's fairly spartan but it's a good proof-of-concept. Let's restart our logstash process with an additional option:

java -jar logstash-%VERSION%-monolithic.jar agent -f logstash-simple.conf -- web --backend elasticsearch:///?local
java -jar logstash-%VERSION%-monolithic.jar agent -f logstash-simple.conf -- web --backend elasticsearch://localhost/

One important thing to note is that the `web --backend` option is actually its own set of commmand-line options. We're essentially starting two programs in one.
This is worth remembering as you move to an external Elasticsearch server. The options you specify in your logstash.conf have no bearing on the web ui. It has its own options.
Expand Down Expand Up @@ -175,7 +175,7 @@ Put this in a file called "logstash-complex.conf"

Now run it all (again. Be sure to stop your previous Logstash tests!):

java -jar logstash-%VERSION%-monolithic.jar agent -f logstash-complex.conf -- web --backend elasticsearch:///?local
java -jar logstash-%VERSION%-monolithic.jar agent -f logstash-complex.conf -- web --backend elasticsearch://localhost/

Point your browser at <http://yourserver:9292> and start searching!

Expand Down

0 comments on commit 81e6952

Please sign in to comment.