C C Magnus Gustavsson

Just bit me too. A colleague wanted to specify that eight remote checks are dependent on one remote check. It didn't work. Took me a long while to realize it...

Personally, I think autodetection should be used, since it's more user-friendly and has negligible overhead. I'm more of a Python guy and pretty far from fluent in Perl, so somebody...

Also, OIDs for FQDD (preferably DisplayName?) need to be added for all storage checks, and used instead of controller id. So quite a bit of code rewriting there.

And systemStateEventLogStatus is missing for iDRAC, so I guess check_esmlog_health can't be used. physicalDiskState (1.3.6.1.4.1.674.10892.5.5.1.20.130.4.1.4) also has completely different values than arrayDiskState. For example, 2 means "failed" for arrayDiskState but...

Fully agree on the `network` option being unnecessarily confusing (and just taking a list of interfaces sounds reasonable to me).

Ah. Just realized that SNI maps are still in INI files. Only jobs are moved to DB. But still, need to handle those as well.

> There might be multiple PostgreSQL clusters installed with different versions. Debian has `pg_lsclusters` script. RHEL doesn't unfortunately, so we can't depend on it for this. A quick Google search...

> I think in this case it's fine to only have a 80% solution. If it works for the common setups and the edge cases are documented, that is fine...

> The version is already available in the globals as `$postgresql::globals::version`. By default detected rather statically but if you need a non-standard version then you modify it. The further code...

Debian appears to have `pg_config --version` as part of the standard installation. I believe that could perhaps solve the problem of making this work on the major Linux platforms. I...