[dev.icinga.com #3441] wrong escalation notification due to state based escalation range behaviour changes #1165
Comments
Updated by fmbiete on 2012-11-13 17:21:18 +00:00 host-name service-name OK 13-11-2012 18:04:27 fmbiete-n1 service-notify-email 80.54 |
Updated by mfriedrich on 2012-11-25 12:45:34 +00:00
any test configs and/or debug logs for that? it possibly requires more debugging, so don't expect it to be fixed within 1.8.2 as this is already in the release cycle.
|
Updated by fmbiete on 2012-11-25 17:19:55 +00:00 Config. Add some host to hostgroup domain-routers-cpds, and contacts to the contacts_group
|
Updated by fmbiete on 2012-11-25 17:29:21 +00:00 Log: Warning is set to 95, Critical to 100
|
Updated by mfriedrich on 2012-11-25 23:16:14 +00:00
can you test the attached git patch? it applies on top of 'mfriedrich/core' and likely 'next' too. it reverts some changes and makes state based escalation ranges on the escalation is valid for notification checks an optional filter then. haven't tested that now, as i am lacking off time to do so. |
Updated by mfriedrich on 2012-11-25 23:25:11 +00:00
|
Updated by fmbiete on 2012-11-26 09:52:27 +00:00 I have applied the path without enabling the new parameter
I will post the results. Thank you very much |
Updated by mfriedrich on 2012-11-26 13:08:15 +00:00
it's likely the behaviour state change, so the revert to the disabled default should fix it. but as usual, test it til tuesday night, so it could be added to 1.8.2 |
Updated by alexbrueckel on 2012-11-26 14:39:22 +00:00 I've applied the patch to a dev system and now the original problem seems to be solved. But: as far as i can see, if notifications escalate, only the last escalation group gets the recovery, the normal contact and escalation groups in between get nothing after critical. |
Updated by fmbiete on 2012-11-26 17:47:06 +00:00 That seems to fix the problem in my system. The recovery is sent only to the last level in the escalation. Thank you very much |
Updated by mfriedrich on 2012-11-28 14:25:31 +00:00
|
Updated by mfriedrich on 2012-11-28 14:35:41 +00:00 alexbrueckel wrote:
that's likely to be reproduced in a different issue, please report so, and add all valuable test config, logs, tests, etc. i've added 3441.cfg to the issue which contains partly config from the reporter, but actually working with the default 'make install-testconfig'. thanks for the tests, then it will apply to 1.8.2 |
Updated by mfriedrich on 2012-11-28 14:41:37 +00:00
|
Updated by mfriedrich on 2012-11-28 15:11:20 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3441
Created by fmbiete on 2012-11-13 17:18:07 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2012-11-28 15:11:20 +00:00)
Target Version: 1.8.2
Last Update: 2012-11-28 15:11:20 +00:00 (in Redmine)
Hi,
I have some tests with notification escalation.
1st notification goes to a dummy contact
3rd notification goes to a level 1 contact
10th notification goes to a level 2 contact
15th notification goes to a level 3 contact
We are seeing a warning notification to level 1.
Before it gets to level 2 limit the problem gets resolved.
A recovery notification is sent to level 1, level 2 and level 3.
Why??
Icinga 1.7.2 didn't have that problem.
Specs:
Debian Squeeze 32 bits
Icinga 1.8.1 + IDOUtils
Mysql 5.5
Changesets
2012-11-28 14:37:56 +00:00 by mfriedrich a881643
Relations:
The text was updated successfully, but these errors were encountered: