[00:16] <lazyPower> noise][: I have
[00:17] <lazyPower> noise][: are you just looking for a specific charm to get started with? cs:trusty/logstash cs:trusty/elasticsearch and cs:trusty/kibana should provide everything needed to provide the core infra.
[00:17] <lazyPower> there's been some work on logstash-forwarder (the GO log forwarder) - or you can use logstash-agent if you dont mind taking the java memory footprint hit.
[01:08] <noise][> lazyPower: problably missed you now, but yes, was looking at the diff between logstash proper (which can send direct to ES) vs forwarder (needing to have sep. logstash indexers)
[07:57] <LinStatSDR> hello
[07:58] <LinStatSDR> hello
[07:59] <LinStatSDR> getting a crazy bootstrap error saying invalid hardware information for node
[07:59] <LinStatSDR> ERROR cannot start bootstrap instance: getInstanceNetworkInterfaces failed: invalid hardware information for node "/MAAS/api/1.0/nodes/node-db43f8cc-79f2-11e4-9246-90e6bad76540/"
[15:00] <jackweirdy> Hey all.  Following the docs here: https://juju.ubuntu.com/docs/authors-charm-writing.html
[15:01] <jackweirdy> $ juju charm create vanilla
[15:01] <jackweirdy> ERROR unrecognized command: juju charm
[15:01] <jackweirdy> Any ideas? Output of juju --version is 1.20.7-unknown-amd64
[15:02] <rick_h_> jackweirdy: you need to install charm-tools to have that available
[15:02] <jackweirdy> Thanks. I'm on macos - do you know if that is in homebrew? :)
[15:03] <jackweirdy> oh, yeah it is (brew install charm-tools). Thanks :)
[15:03] <thebozz> Hey guys, is there any plan to support more advanced configurations in the ELK charms? I'd like to customize ES clusters better, and the Logstash charm is kind of lacking as it is right now.
[15:11] <jackweirdy> Hmm, the command exists, but when I run the create command I get an OSError because a file is missing. Can't decipher it though https://gist.github.com/NotBobTheBuilder/e3f3e02796889692b3a4
[15:12] <rick_h_> jackweirdy: hmm, can you file a bug https://github.com/juju/charm-tools ?
[15:12] <jackweirdy> Sure can :)
[15:13] <rick_h_> ty!
[15:19] <lazyPower> thebozz: I'm kind of a maintainer of the ELK stack when i have time to work on it - pull reuqests are welcome for any features you want to add
[15:19] <mwak> hi
[15:20] <thebozz> lazyPower: alright! We're still setting up our MAAS/Juju cluster, but as soon as I can get my hands on it I'll start experimenting and committing stuff.
[15:21] <lazyPower> thebozz: sounds great :)
[15:21] <lazyPower> hello mwak
[17:39] <noise][> lazyPower: is there a version of the logstash charm that has lumberjack input enabled, for use with logstash-forwarder?
[17:40] <lazyPower> noise][: the current edition in the store only supports logstash-agent, and has a redis-backend
[17:40] <noise][> everything I'm finding seems to be using redis to shuttle between logstash-agent and logstash-indexer
[17:40] <noise][> ok, so I'll have to fork it then
[17:41] <lazyPower> noise][: the other options haven't been developed as far as I know. However lumberjack + the logstash-forwarder would be a welcome feature
[17:41] <noise][> ok, thanks for confirming
[17:41] <lazyPower> noise][: yeah, branch it - implement a new relationship that implements reconfiguring for lumberjack and I'd happily review it
[17:43] <noise][> lazyPower: i'm pretty new to charms so i might just hack it to include lumberjack input, take a port option, and leave config on the forwarder side manual (as it is in https://jujucharms.com/u/chris-gondolin/logstash-forwarder/trusty/6 currently)
[17:44] <lazyPower> noise][: nobody benefits when you do it that way :) I'm here to help if you decide to commit changes back.
[17:45] <noise][> lazyPower: agreed, let me see what I can do :)
[19:29] <lazyPower> note to self, do not run bundletester and wonder why its hanging up when you'r ein an active debug-hooks session trapping hooks
[19:29] <lazyPower> >.>