Hi,
I had been running
the current Stable (1.20) and just installed the OMD nightly from 2015-06-13
(1.12.20150613), mainly for the fix for Backup Copy jobs being shown as Unknown
status when Idle. This version has fixed that.
Now it appears that
the newest version has introduced the “Time since last backup” check
for veeam_client.
I have a job that
only runs once per week, so the time since last backup is over the default thresholds
if 30hrs and 2 days.
I have tried to make
a new rule with WATO for this particular job to WARN at 7 days, 6 hours and CRIT
at 8 days, 6 hours, but when I try to activate the rule I get the following
error:
Error creating
configuration: Invalid entry ‘({‘age’: (626400, 691200)}, [], [‘S-PRINT’],
[u’Tier 2 VM Backups \\(Weekly\\)$’])’ in host configuration list: must have 2
or 3 entries
I have tried
different values in the WARN and CRIT levels and tried with and without
specific servers, but I always get “must have 2 or 3 entries”
Is this a known
issue or is there something I can do to create this rule?
Thanks!
I just tried again.
When I enter the job name in
WATO, there is only a single backslash. Here is a direct copy from the text
box: Tier 2 VM Backups (Weekly)$
The extra backslashes are only appearing
in the error message.
···
From: Pinkoski, David
[mailto:dPinkoski@michigan.com]
Sent: Wednesday, June 17, 2015 2:57 PM
To: Ian Middleton; checkmk-en@lists.mathias-kettner.de
Subject: RE: veeam_client Time since last backup rule error
Try a single backslash?
Backups
\(Weekly\)$’])
Change to
Backups
(Weekly)$’])
From: checkmk-en-bounces@lists.mathias-kettner.de
[mailto:checkmk-en-bounces@lists.mathias-kettner.de] On Behalf Of Ian
Middleton
Sent: Wednesday, June 17, 2015 2:53 PM
To: checkmk-en@lists.mathias-kettner.de
Subject: [Check_mk (english)] veeam_client Time since last backup rule
error
Hi,
I had been running
the current Stable (1.20) and just installed the OMD nightly from 2015-06-13
(1.12.20150613), mainly for the fix for Backup Copy jobs being shown as Unknown
status when Idle. This version has fixed that.
Now it appears that
the newest version has introduced the “Time since last backup” check
for veeam_client.
I have a job that
only runs once per week, so the time since last backup is over the default
thresholds if 30hrs and 2 days.
I have tried to make
a new rule with WATO for this particular job to WARN at 7 days, 6 hours and
CRIT at 8 days, 6 hours, but when I try to activate the rule I get the
following error:
Error creating
configuration: Invalid entry ‘({‘age’: (626400, 691200)}, [], [‘S-PRINT’],
[u’Tier 2 VM Backups \\(Weekly\\)$’])’ in host configuration list: must have 2
or 3 entries
I have tried
different values in the WARN and CRIT levels and tried with and without
specific servers, but I always get “must have 2 or 3 entries”
Is this a known
issue or is there something I can do to create this rule?
Thanks!