Hi,
I am looking for hints, pointers, URLS about collecting puppet metrics and
agent status using logstash filters?
kind regards
Walid
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiv
Thank Bill, will take a look
On 7 August 2014 16:18, Bill Fraser wrote:
> Hi Walid,
>
> I *think* this may be what you're looking for:
>
> https://github.com/logstash/puppet-logstash-reporter
>
> It is a Puppet report handler that sends event and metric details of
&g
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 wrote:
> We still use Puppet Dasboard (with PuppetDB)
what if you run via cron? in my case I had a similar issue but it was
mcollective agent when there was an intermittent issue with the network
On 29 August 2014 17:59, pmorel wrote:
> Hello,
>
> Recently 3 puppet agents instances (on 3 different servers yet with
> quasi-similar configurations)
you would need the exec resource to execute the "who -b" and filters you
apply to it
On 29 October 2014 20:09, Erik Ritzman wrote:
> I am fairly new to DSP and am experimenting as I follow along with the
> Puppet Tutorial
>
> Playing off of the Task 1 in the Conditionals section...
> my conditi
Hi Erik,
What was the largest practical number of nodes tested against it, or
configured.
Best regards,
Walid
On 26 August 2014 16:04, Erik Dalén wrote:
> A new release of Puppet Explorer is out. It includes a new look which you
> can check out at the new public demo site
could it be the version of yum on these nodes? why not have the proxy
configuration ( user, password, and url) managed by puppet too. i am
assuming you are using yumrepo resource.
On 6 November 2014 20:57, wrote:
> Greetings
>
> This is my first post here, so hi everyone!
>
> I have been using
it would be some::fun_setup::sname or more specifically
:: some::fun_setup::sname or $:: some::fun_setup::sname
On 7 November 2014 05:30, wrote:
> In puppet 2.7 we use the following construct.
>
> define some::fun(
> ensure => present,
> sname => 'some.server.com'
> ) {
> include some::fun
Congratulations Felix, I just saw it in my safari books online, checked few
topics, and found it brief and informative,
Thank you,
Walid
On 30 November 2014 at 17:24, Felix Frank
wrote:
> Hi all,
>
> it's with great pride that I follow Alessandro with yet another plug of
> re
for the code manager replacement we use r10k, nfs share, ssync, and
gitlab-ce with webhooks. we stopped using mcollective
On 26 April 2016 at 14:08, Geoff Galitz wrote:
>
> Thanks for your replies.. much appreciated.
>
> -G
>
>
>
> On Thu, Apr 21, 2016 at 3:40 PM, Ryan Anderson
> wrote:
>
>> Th
the node usually shows unresponsive if it did not report back within the
unresponsive threshold time, how often you are running the agents, and how,
what is the frequency of reports already received?
On 25 April 2015 at 03:48, wrote:
> Hi,
>
> I am using open source Puppet 3.7.3 with Dashboard.
Hi Trevor
the link is not working for me, it points to three blogs none of them are
related to mco
thanks,
Walid
On 14 May 2015 at 05:10, Trevor Vaughan wrote:
> Hi All,
>
> I presented a piece on a proof of concept that I put together to perform
> OpenSCAP scans against s
, the idea is deploy, test, tune,
and tear apart the infra until certain requirements are met to automate the
build, tuning, and configuration.
Best regards,
Walid
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from
Hi Philip,
open source puppet 3.x documentation seems to have stopped updating in
favour of PE documentation as per puppet support. that project is not
handled by me any longer, my colleagues have gone with foreman, it's
bootstrapping and scaling is very flexible, it is already a distributed
archi
know if
one is testing Puppet environments only what are merits and cons of
test-kitchen vs. Beaker, given that beaker seems to have matured more since
the last year, our toolset will involve bare-metal "ssh", vagrant/libvirt,
and docker.
Best regards,
Walid
On 28 August 2015 at 1
it depends on how big your infrastructure is. these are recommended for
larger infra, there is also the new way of using partitioned mcollective
and using hubs, and spokes, it all depends, you can find about hubs, and
spokes in here
https://docs.puppetlabs.com/pe/latest/install_add_activemq.html
The alternative for spacewalk would be foreman, foreman can do linux
provisioning (bare metal, docker, vms), and can do configurtion managment
and reporting, as well as scalable and was built with the assumption of
distributed data centers. in terms of configuration managment foreman uses
currently
17 matches
Mail list logo
