https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • j
    There is a postgres process that seems to say puppetdb in the process list
  • j
    curl <http://localhost:8080/pdb/query/v4/nodes>
    This seems to list a lot of things. Is that what you're referring to?
  • n
    I’m not sure your version of PuppetDB is new enough to support the PQL query syntax, but something like this is what you’d want to find nodes that haven’t checked in since X days: https://puppet.com/docs/puppetdb/5.2/api/query/examples-pql.html#timestamp-filtering
  • b
    for query examples, also take a look at https://voxpupuli.org/docs/pql_queries/ . If you write your own query, let me know and I will add it to the list (or send us a PR)
  • n
    curl -X GET <http://localhost:8080/pdb/query/v4> --data-urlencode 'query=nodes[certname] { report_timestamp <= "2022-10-05 00:00:00" }'
  • n
    curl -X GET <http://localhost:8080/pdb/query/v4> --data-urlencode 'query=nodes[certname] { report_timestamp <= "2022-10-05 00:00:00" }'
  • j
    puppet query "nodes[certname,report_timestamp] { report_timestamp >= '$(date --date '7 days ago' +'%Y-%m-%dT%H:%M:%S')' }"
    This seems like what I want. Thanks.
  • j
    Doesn't even need the report_timestamp in the nodes object, that was just error checking
  • v
    we use 
    catalog_timestamp
    instead
  • j
    Because that's the last time puppet successfully ran as opposed to just checkin?
  • v
    Copy code
    old_timestamp=$(date -u -d '-7 days' -Isec)
/opt/puppetlabs/bin/puppet-query "nodes[certname]{catalog_timestamp < \"$old_timestamp\"}" | jq -r '.[].certname'
  • v
    I guess one could use no-report setting on agent
  • j
    I doubt we are doing that here, but yes, that could be a concern. This should be good enough. Thanks. 
    puppet query "nodes[certname]{catalog_timestamp > '$(date -u -d '-7 days' -Isec)'}" | jq -r '.[].certname' | sort > active_puppet_servers.txt
  • l
    that nodes endpoint is how I do half my reporting / alerting for nodes not checking in
  • w
    is this syntactically correct?
    Copy code
    if $::osfamily =~ '(Redhat|Debian)' {
  • w
    is this syntactically correct?
    Copy code
    if $::osfamily =~ '(Redhat|Debian)' {
  • w
    hmm, the escape positioning is throwing me off some.
    Copy code
    if $trusted['certname'] =~ /^www(\d+)\./ {
  notice("Welcome to web server number $1.")
}
  • n
    It’s syntactically correct, but won’t do what you think it will since you’re comparing that to a String rather than a Regex
  • w
    got it,
    Copy code
    if $::osfamily =~ /(Debian|RedHat)/ {
  • n
    Copy code
    if $facts['os']['family'] in ["Debian", "RedHat"] {

}
    I like 
    in
    for checking multiple strings, personally.
  • n
    if $facts['os']['family'] in ["Debian", "RedHat"]
    I like 
    in
    for checking multiple strings, personally.
  • n
    Copy code
    if $facts['os']['family'] in ["Debian", "RedHat"] {

}
    I like 
    in
    for checking multiple strings, personally.
  • n
    It’s syntactically correct, but won’t do what you think it will since you’re comparing that to a String rather than a Regex
  • w
    What's the functional difference between this example and the prior one I had hacked together?
  • n
    No functional difference. But I find it simpler to add strings to an array than to combine regexes with 
    |
    .
  • n
    Well, the other change is to use the 
    $facts
    hash. That has a functional difference in that it’s more stable across Puppet versions (especially future versions).
    ➕ 1
  • g
    you would probably also want to put anchors on the regex version eg:
    Copy code
    if $facts['os'['family'] =~ /^(Debian|RedHat)$/ {
    ie: to match 
    Debian
    or 
    RedHat
    exactly (whereas w/out anchors it could match 
    someDebianwithsuffixtrailing
    etc
    ➕ 1
  • g
    +1 what Nate said about syntax to reference facts
  • n
    Oh! Yeah, thanks @glee. Thanks a very important functional difference. Your regex would’ve matched “foobarDebianlkjasd”. But the 
    in
    operator does full-string comparison.
    ➕ 1
  • w
    Ahhhhhhh yea
1...195196197...428Latest