https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • s
    This message was deleted.
    v
    • 2
    • 1
  • m
    of if using PE you can use the now built in agent status check function https://forge.puppet.com/modules/puppetlabs/pe_status_check/readme#fact-agent_status_check
  • m
    if using puppet open source you could consider applying a custom fact modeled on the PE counterparts: https://github.com/puppetlabs/puppetlabs-pe_status_check/blob/e810875b317b444cd996fa97b7458219cdcf4746/lib/facter/pe_status_check.rb#L113 and https://github.com/puppetlabs/puppetlabs-pe_status_check/blob/e810875b317b444cd996fa97b7458219cdcf4746/lib/facter/pe_status_check.rb#L124 the two facts above check if an agent produced a report in the last runinterval and check if a catalog apply successfully on last puppet run
  • s
    This message was deleted.
    y
    s
    r
    • 4
    • 4
  • l
    for monitoring puppet agent, I've used a report module to zabbix_send metrics to a zabbix infrastructure
  • l
    then the puppet server updates monitoring based on real runs
  • s
    This message was deleted.
    c
    • 2
    • 1
  • s
    This message was deleted.
    đź’Ş 1
    v
    b
    +5
    • 8
    • 9
  • s
    This message was deleted.
    b
    c
    • 3
    • 3
  • s
    This message was deleted.
    r
    • 2
    • 1
  • r
    How do you guys monitor puppet’s successful runs? Like, how do you something’s failing..? I was going with puppetboard, but it seems to be missing failures and not showing them...
  • b
    we had a similar topic I think last Friday, you should be able to see that in the backlog
  • b
    tl;dr a few options are available. you can check on each node as mentioned above. you can query puppetdb or foreman
  • r
    I’m surprised puppetboard is not showing it. I thought that was one of it’s “jobs”.
  • r
    I’ve posted about it on #C0W1Y5VL0, but didn’t get any responses.
  • s
    This message was deleted.
    v
    b
    +2
    • 5
    • 67
  • b
    that's the key functionality
  • r
    like puppetboard wouldn’t notify me, but i’d be able to see if there is a failed puppet run.
  • r
    puppet-agent is definitely failing on a server, but it’s not under puppetboard Failures.
  • s
    This message was deleted.
    r
    b
    • 3
    • 3
  • b
    didn't it submit any reports maybe?
  • s
    This message was deleted.
    Untitled
    r
    k
    • 3
    • 8
  • d
    fry dancing Content and Tooling is about to start up in #CFD8Z9A4T
  • s
    TIL: to properly report if a machine is virtual or not, the 
    virt-what
    package is required. Did I miss any hint on that in some README? It's neither a dependency of the 
    puppet-agent
    package nor recommended.
  • v
    Hmm, we don't have it deployed anywhere and yet facter is correct
  • b
    that should be part of the puppet AIO packages
  • v
    Learned something today
    Copy code
    $ rpm -ql puppet-agent|grep virt-what
/opt/puppetlabs/puppet/bin/virt-what
  • s
    This message was deleted.
    a
    • 2
    • 1
  • s
    @bastelfreak interesting. It's in there, but facter is unable to find it thinking
  • s
    Ha, it's even better: it's happening only on a fresh install. After the first run is complete, it's working.
1...383384385...428Latest