#logstash

whack, doing make docs from clean pull does interesting things.. (doing a make tarball now)

imperialwicket: ah, as a direct parameter? i.e. `bin/logstash -Xms256m -Xmx1024m`?

imperialwicket: this works: `ES_MIN_MEM=128m ES_MAX_MEM=256m bin/elasticsearch`, but passing in -Xms to either logstash or elasticsearch don't work. Nor does `LS_MIN_MEM=128m LS_MAX_MEM=256m bin/logstash`

it's just LS_HEAP_SIZE on bin/logstash

thanks, i usually defer to electrical's implementation in puppet-logstash

whack is likely a better reference!

ok whack, since you're here - make docs == no such file to load -- kramdown

thanks whack

coolacid: gem install kramdown, yo

I installed the gem, ran make tarball, I see the gem in venors under JRUBY still nothing

imperialwicket: hmm puppet-logstash, you say

no idea, we haven't really attended to docs building as an easy way for new folks to do things

Title: elasticsearch/puppet-logstash · GitHub (at github.com)

shoerain ^

whack, not that I blame you

I blame you! ;)

Yes, well..

My lack of ruby skeeels is lacking. ;)

Must go to dinner before wife kills me.. outtie

cool, logstash and elasticsearch behave well with low memory constraints. is it just normal to request memory when the load increases?

does logstash just drop events if it can't keep up and I'm not using redis?

shoerain: logstash should never drop events

isn't there a point when throughput is too high for a logstash node to keep up with?

yes

there are other options at peak-throughput than dropping things on the floor ;)

I'm just trying to tune/figure out that point so I know when to add more nodes

Oh really? cool

I guess there's some documentation I should look at for that?

I can tell that my 384MB vagrant machine doesn't like `cat access.log | pv -L 500000 | nc localhost 3333`. pv keeps giving me wildly varying throughput

howdy, folks!

I'm going through the logstash tutorial, and one of the instructions (granted, an aside) doesn't work as expected.

Running 'bin/plugin -install lmenezes/elasticsearch-kopf' is expected to return some sort of happy success message, followed by http/elastic access to a shiny interface on local:9200/_plugin/kopf

instead I just get 'Can only install contrib at this time... Exiting.'

lz-dylan: you're not the first

hm

lz-dylan: however, it works for me. What's in `elasticsearch-directory/plugins/`?

can you give me a full path?

I'm brand spankin' new with logstash

(and find(1) doesn't find that as a subdirectory of logstash at all)

Oh, did you download elasticsearch? search for the second `curl` command on http://logstash.net/docs/1.4.0/tutorials/gettin...

<http://tinyurl.com/oyqwfvr>; (at logstash.net)

@shoerain I just installed it with the deb package

installed es version is 1.1.1

ls

and wrong window.

lz-dylan: you executed the wrong plugin command. You did the LS one instead the ES one

any plans on making logstash live reload configs?

Can I do better than 20 events/second on a 4096MB vm and a standard HDD (presuming CPU is not so relevant)? ES, LS are both running on the same vm.

patarr: would probably be better to have logstash react to SIGUSR1, I think

well right, reload upon some sort of signal.