Beaver fails to start about chef-logstash HOT 7 CLOSED

This actually affects everything tried: 0.6.1, 0.7.0, master branches

Edit: ok seems to be the transport is not set, by default we should use rabbitmq probably?

from chef-logstash.

I do not use this recipe nowadays, so I could be wrong. But this is what I remember:

Transport is chosen from the node['logstash']['beaver']['outputs'] attribute, which should be an array of hashes. See the example in the README.

Only the following transports are supported by the beaver recipe (I don't know if beaver currently supports more transports):

• amq
• redis
• stdout
• zmq

See the code of the recipe for more information. outputs array is filled there.

Setting a default transport doesn't make sense to me.

from chef-logstash.

I thought intention of this cookbook, to provision logstash server and client, which starts to work instantly without any configuration..? You already taking logstash_server node IP, from node state in beaver recipe, why not to take all credentials you need if you pick one of the outputs/inputs for server/client?

Let's say I have two roles: logstash_client and logstash_server, one has logstash::agent, another one has logstash::server recipes. Without specifying any attributes at all, i've got working logstash-server/client out-of-the-box. This doesn't makes sense to you?

from chef-logstash.

By the way this pull request seems to be updated readme file in a better manner :) #186

from chef-logstash.

I thought intention of this cookbook, to provision logstash server and client, which starts to work instantly without any configuration..? You already taking logstash_server node IP, from node state in beaver recipe, why not to take all credentials you need if you pick one of the outputs/inputs for server/client?

I do not know if I understood this paragraph correctly.

The transport in the beaver recipe is calculated from the outputs attribute. If this attribute is empty, cannot be calculated. The outputs are required by beaver to run, but not by logstash agent.

Let's say I have two roles: logstash_client and logstash_server, one has logstash::agent, another one has logstash::server recipes. Without specifying any attributes at all, i've got working logstash-server/client out-of-the-box. This doesn't makes sense to you?

Maybe I'm wrong on this point. AFAIK, that's because logstash agent works out of the box, beaver not. That is, logstash agent can be started without any outputs, beaver cannot. That's the problem, right?

But I see your point. I have not a clear answer to the problem. Perhaps starting beaver with some defaults may be a good idea, but I have not clear what values to set as default. Beaver can be started only with one transport and its behavior is different from logstash agent. It does not completely replace logstash agent. At least that was the last time I used it.

from chef-logstash.

M, so I still need to configure logstash_server to accept some kind of specific input from beaver right? Ok understood. This makes sense :)

P.s. Without #187 logstash::agent fails for me in all branches. Maybe this has something to do with Chef version. I'm using latest one.

from chef-logstash.

M, so I still need to configure logstash_server to accept some kind of specific input from beaver right? Ok understood. This makes sense :)

You need to configure beaver to output to, for example, amq. Then you configure logstash server to read from amq.

from chef-logstash.