Hi Martijn

are you using the logstash reporter
https://github.com/logstash/puppet-logstash-reporter , would it be possible
to share your puppet kibana dashboards, and logstash.conf file

regards

Walid


On 27 August 2014 19:54, Martijn <[email protected]> wrote:

> We still use Puppet Dasboard (with PuppetDB) to get a quick overview of
> the state of nodes and the logs of their Puppet runs. Not very fancy and a
> little hard to search, but it works well as a read-only dashboard.
>
> Furthermore we use the ELK-stack (Logstash, Elasticsearch, Kibana) (See
> http://www.elasticsearch.org/overview/), which is essentially an
> open-source alternative to Splunk, to ship all logs from each host via a
> queue to a central server, where they're normalized, processed and stored
> in Elasticsearch. I've created several dashboards in Kibana that query that
> data to graph metrics and show anomalies, not just for Puppet runs. I'd
> prefer to add some active alerting to this pipeline, but have yet to figure
> that out.
>
> There are many ways to do this, but this works pretty well for us.
>
> Regards, Martijn
>
>
> Op dinsdag 26 augustus 2014 19:34:51 UTC+2 schreef Mike Reed:
>
>> Hello all,
>>
>> I've recently been looking into various methods for configuring
>> meaningful logging from my puppet 3.6 master/agent nodes.  I've typically
>> gone the route of grep'ing through syslog on both master/agents and I'd
>> like something a little more robust and user friendly for other who may not
>> be hip on going through hundreds of lines of syslog information in addition
>> to a simpler design.
>>
>> I've recently been playing with an agent's puppet.conf and simply trying
>> to set the logdir using this with no success at all (permissions have been
>> changed to allow puppet to write to that directory):
>> [agent]
>> logdir=        /var/log/puppet
>>
>> I've also tested syslog facility configurations but after some time, it
>> seemed like having to modify multiple configuration files to get puppet
>> logging consistent, seems a bit bulky to me.
>>
>> I suppose I have two questions:
>>
>> 1.  Is there a simple way to push messages to a file other than
>> /var/log/syslog on an Ubuntu machine?
>> 2.  Is there a preferred way in the community by which people aggregate
>> logs to make troubleshooting nodes issues easier to manage?
>>
>> Thank you all for your time in advance.
>>
>> Cheers,
>>
>> Mike
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/59be2841-9cf1-49cd-ac2d-d219db0e2c38%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/59be2841-9cf1-49cd-ac2d-d219db0e2c38%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAN4dctqzWsG9DJs0X635yqTv34KRbmgcjH5eJPB0TwHVwcVVFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to