mape2k / check_mk_extensions Goto Github PK

Thank you for your CheckMK nut Plugin. I installed the agent file (nut) on the host and I got information about the ups.
But when I try to get the service into checkmk, I got this issue during the discovery:

WARNING: Parsing of section nut failed - please submit a crash report! (Crash-ID: 7f36e572-a61b-11ed-ab44-00155d4d190e)

Hallo,
ich hab cmk 2.1.0p19 auf einer ubuntu vm installiert und kann den nut server (synology nas) per upsc abfragen

upsc [email protected]
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 10
battery.charge.warning: 50
battery.runtime: 4860
battery.runtime.low: 120
battery.type: PbAc
battery.voltage: 26.8
battery.voltage.nominal: 24.0
device.mfr: American Power Conversion
device.model: Smart-UPS 750
device.serial: 1234567890
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 5
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: DSM7-1-1-42930-workplus-version2-repack-42930-220712
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.firmware: UPS 09.3 / ID=18
ups.mfr: American Power Conversion
ups.mfr.date: 2016/06/09
ups.model: Smart-UPS 750
ups.productid: 0003
ups.serial: 1234567890
ups.status: OL
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.vendorid: 051d

habe nut mkp installiert
OMD[prod]:$ mkp list
nut
OMD[prod]:$

wenn ich die synology nas neue services discovery taucht nichts auf?

was muss bei parameters unter UPS eingegeben werden?

bitte danke

Check_MK 1.5.x got rid of the checkgroup_of dictionary. So using your plugin breaks Check_MK.

The service scan shows:

Invalid check parameter: Undefined key 'length' in the dictionary. Allowed are deferred, active.! The parameter is: {'deferred': (10, 30), 'length': (10, 20), 'age': (3600, 7200), 'size': (1048576, 2097152)} The variable name is: checkgroup_parameters:mailqueue_length

In that version of Check_MK, you can actually define mailqueue_length parameters in the rules - but only deferred and active limits, no age or length.

Using on Pi w/NUT to monitor two UPS devices in the same home lab area, in Checkmk both are identified correctly by name as two services, however they are both using the same service performance data from ==> Tripplite-Rack <== in the GUI effectively meaning one UPS is not monitored.

---editied to relevant info per UPS---

pi@pihole:/usr/lib/check_mk_agent/plugins $ ./nut
<<>>
==> Tripplite-Network <==
battery.charge: 100
battery.runtime: 5760
battery.type: PbAC
battery.voltage: 13.5
battery.voltage.nominal: 12.0
device.mfr: Tripp Lite
device.model: Tripp Lite UPS
device.type: ups
input.frequency: 60.0
input.voltage: 120.3
input.voltage.nominal: 120
output.frequency.nominal: 60
output.voltage.nominal: 120
ups.beeper.status: enabled

==> Tripplite-Rack <==
battery.charge: 100
battery.runtime: 4050
battery.type: PbAc
battery.voltage: 26.9
battery.voltage.nominal: 24.0
device.mfr: Tripp Lite
device.model: TRIPP LITE UPS
input.frequency: 59.8
input.voltage: 120.1
input.voltage.nominal: 120
output.frequency.nominal: 60
output.voltage.nominal: 120
ups.beeper.status: enabled

Hallo,

ich möchte dein Plugin gerne dazu verwenden einen Backup Job mit rsync zu überwachen, leider passt hier aber der "Service state" dann nicht (ist genau umgekehrt) Idealerweise wäre zB: "New Files:0" OK alle anderen Werte dann WARN/CRIT.
Kann ich das irgendwie einstellen oder kannst du mir sagen wie ich das plugin anpassen kann?

Dear Marcel,

I'm glad I found your lnx_backup check plugin, ad I am grateful for the work you've already done.

We are using check-mk raw edition, and I was able to install lnx_backup-2.0.mkp through the command line.

Also, I was able to figure out the basic usage, e.g.
/opt/omd/sites/MYSITE/local/share/check_mk/agents/lnx_backup BACKUP_NAME duply duply default status
gathers backup status and statistics and writes this data to
/var/lib/check_mk_agent/lnx_backup/BACKUP_NAME
, while
/opt/omd/sites/MYSITE/local/share/check_mk/agents/plugins/lnx_backup
is the actual agent plug-in which inserts the data from
/var/lib/check_mk_agent/lnx_backup/BACKUP_NAME
into the check-mk-agent output.

So, I assume I have to first download
/opt/omd/sites/MYSITE/local/share/check_mk/agents/plugins/lnx_backup
to the monitored host and place it into
/usr/lib/check_mk_agent/plugins/.

But what should I do with
/opt/omd/sites/MYSITE/local/share/check_mk/agents/lnx_backup
?

Should I use it as a wrapper for the actual duply cronjob on the monitored machine?
Or should it run in parallel?
Or is it invoked by check_mk_agent by any means?

That''s the part that is not really clear to me.

Thanks for your help,
and all the best for 2023!
Andreas