PuppetDB: 4.2.2
icingaweb2-module-puppetdb: 14afc2a
Query Type Nodes
Resource Type Host

Same as #2. Created new issue since that one was closed.

When adding the PuppetDB output, everything seems OK, except that preview does not present any facts in any other colums than the "massive" facts one.

Here's a screenshot. The column names are a bit mangled because wasn't easy to take a scrolling screenshot but you can see the empty columns.

Trying to apply modifiers to the single facts does not yield any different results either.
The module correctly guesses classes, nodes, resources and the name of the facts but it does not return the data from them.

Individual fact columns are empty so they're not able to be imported as-is or modified in any way. Hope this clarifies the issue. Let me know if you need more info and i'll try to provide.

Hi, I’m using icingaweb2-module-puppetdb to import my nodes from puppetdb. Works very nice! Now I would like to use facts from puppetdb in icinga in order to adjust the thresholds for certain checks. For example, load check needs warnings and critical thresholds. For each client I know how many cpu’s are configured (processercount fact from puppet). I want to use this value and dynamically configure the several thresholds according to this value. I already have a data field for every threshold (load_cload1 etc). I use modifiers to map the fact to load_cload5) in icinga. Now I'm trying to use load_cload5 to configure load_wload5, load_cload1 etc.
Is this possible?

Environment

• Module version (System - About):
  1.0.0
• Icinga Web 2 version and modules (System - About):
  2.4.2-1.xenial
• Icinga 2 version (icinga2 --version):
  2.7.1-1.xenial
• Operating System and version:
  xenial
• Webserver, PHP versions:
  apache
  php7.1

We saw recently that the imported_property tablet inside the director mariadb database has a size of 15GB. We found out that most of that size comes from all of our puppet facts for each server.
We have a puppetdb with around 2000 nodes in it. The core facts plus some (20 or so) custom facts.

Expected Behavior

I dont know if thats really a bug, but maybe this table or the facts import needs an improvement.

Current Behavior

This lead to a sitution where the backup of this database took 1,5 hours to complete. This lead to a icinga2 crash because database entries from icinga2 were stored in memory to fast and the out-of-memory killer came in.

Possible Solution

As a workaround we excluded this particular table with "--ignore-table=director.imported_property".
Because the data inside isnt really necessary for a backup I guess.

Steps to Reproduce (for bugs)

1. Use PuppetDB as import source
2. Watch the imported_property table

Your Environment

• Module version (System - About): 1.0.0, Director: 1.4.1
• Icinga Web 2 version and modules (System - About): 2.5.1
• Icinga 2 version (icinga2 --version): 2.7.2
• Operating System and version: RHEL 7.5

Hello,

I added the fact.disks and I get in icinga2 something like:

    vars.disks = {
        nvme0n1 = {
            model = "INTEL SSDPEDMD400G4"
            size = "372.61 GiB"
            size_bytes = 400088457216
        }
        sda = {
            model = "Crucial_CT275MX3"
            size = "256.17 GiB"
            size_bytes = 275064201216
            vendor = "ATA"
        }

but for my apply rules, I need also:

path = /dev/<device>

iostats_disk = <device>

Is it possible with the puppetdb module and the sync rules?

cu denny

Any suggestions on how to split facts in arrays to get an output where

Input Example:

[{"Name":"ADSync","StartType":2,"Status":4,"CanShutdown":true,"CanStop":true,"CanPauseAndContinue":false},
{"Name":"AeLookupSvc","StartType":3,"Status":1,"CanShutdown":false,"CanStop":false,"CanPauseAndContinue":false},
{"Name":"ALG","StartType":3,"Status":1,"CanShutdown":false,"CanStop":false,"CanPauseAndContinue":false},
{"Name":"AppIDSvc","StartType":3,"Status":1,"CanShutdown":false,"CanStop":false,"CanPauseAndContinue":false},
{"Name":"Appinfo","StartType":3,"Status":1,"CanShutdown":false,"CanStop":false,"CanPauseAndContinue":false}]

Desired output is a key based on the name with the key/value pairs as a subset, example:

vars.windows_service["ADSync"] = {
    name = "ADSync"
    starttype = 2
    status = 4
    canshutdown = true
    canstop = true
    canpauseandcontinue = false
}

The reasoning behind this is to let Puppet discover services that icinga can monitor. I have a script that emits the services on Windows to Puppet, classifying them (Standard windows service, role (AD/IIS) or 3rd party, letting us quickly monitor anything we dont know about), the same is easily done for IIS' websites and AppPools amongst other examples.
With Director we can then almost automate an approval process for everything in Icinga2, letting everything come in "unclassified" and be monitored from day 0, letting the NOC take care of classifying if its production, dev or test by a process going on after its already being monitored, rather than trying to figure out what is on the box. 👍 👍 👍

Parse error: syntax error, unexpected '(', expecting :: (T_PAAMAYIM_NEKUDOTAYIM)
Seems to be related to FilterRenderer.php, the change from return new FilterRenderer($filter); to return static($filter); at public static function forFilter(Filter $filter)

So far i didn't witness any side effects.

When adding the PuppetDB output, everything seems OK, except that preview does not present any facts in any other colums than the "massive" facts one.

Trying to apply modifiers to the single facts does not yield any different results either.

The module correctly guesses classes, nodes, resources and the name of the facts but it does not return the data from them.
Currently using PuppetDB 4.1.2

Hi,
how to configure sync settings regarding exported variables ? We're using Puppet to generate icinga2 configs, export them to PuppetDB and then collect on icinga master.
We'd like to switch to use this module due to outlined benefits (performance mainly), however when adding new hosts how do we map parameters from PuppetDB into icinga fields, as these already contain all variables?

hi,

I try to add a template to hosts, via based on a fact. It works, if I use "certname=host.foo", but I need something like:

Import template "nginx-template", if facts.puppet_modules=nginx, like I have it on the screenshot.

Is that possible?

cu denny

Please check issue Icinga/puppet-icingaweb2#197.
I'm not sure who should fix that, or if I did anything wrong in my setup.
If it has to be fixed in Icinga/puppet-icingaweb2, then this is just for documentation about the problem when used with Icinga/puppet-icingaweb2.

If you have deactivated the IDO backend including the monitoring module and only activated the IcingaDB front- and backend, you cannot activate the puppetdb module due to an unmet dependency on the monitoring module.

Expected Behavior

Module can be used in environments with IcingaDB

Current Behavior

Module cannot be used in IcingaDB environments at the moment

Possible Solution

Make it IcingaDB compatible :)

Steps to Reproduce (for bugs)

1. Install Icinga with IcingaDB Front and backend only
2. Install Icinga Director
3. Install the Import Source puppetdb
4. Try to activate puppetdb, you see the unmet dependency info

Context

I want to try the puppet importsource in an IcingaDB environment

Your Environment

• Module version (System - About):
  • Director 1.10.2
  • Icingadb 1.0.2
  • puppetdb 1.0.0
• Icinga Web 2 version and modules (System - About): 2.11.4
• Icinga 2 version (icinga2 --version): v2.13.7

Thanks and cheers,
Marcus

PuppetDB 2.3.8, wie in Ubuntu Precise enthalten, kann nur API v3. Die Implementierung von v4 ist experimental und anders, als PuppetDB 3+ das macht. Das Modul funktioniert somit also nur mit der Auswahl v3.

Daher vielleicht bei der Auswahl der API Version die 2.3 mit bei V3 auflisten, nicht bei v4.

hi,

I have three PuppetDBs all with many sync rules and I have to add a new PuppetDB. It would be great, if I can clone / export / import the sync rules.

The documentation here includes the following code block:

exec { "Generate combined .pem file for $puppetdb_host":
  command     => "cat private_keys/${my_certname}.pem certs/${my_certname}.pem > private_keys/${my_certname}_combined.pem",
  path        => ["/usr/bin", "/usr/sbin"],
  cwd         => $ssl_subdir,
  refreshonly => true
}

This won't work as listed due to cat being /bin/cat by standard, and NEVER sbin.

The fix is the following:

exec { "Generate combined .pem file for $puppetdb_host":
  command     => "cat private_keys/${my_certname}.pem certs/${my_certname}.pem > private_keys/${my_certname}_combined.pem",
  path        => ["/usr/bin", "/bin"],
  cwd         => $ssl_subdir,
  refreshonly => true
}