Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Thresholds should work without restart when putting nodes into categories

Description

It should be possible to add nodes into categories which are used for thresholds without restarting OpenNMS to apply the threshold to the node.

 

  • You have working threshold config which is assigned to nodes using a category filter in threshd config.

  • Now you put nodes into this category.

  • Threshold is not working for these nodes.

  • Reloading threshd doesn't work, too.

  • Once you restart OpenNMS the threshold works!

  • Same issue vice versa, if you want to remove a node from a threshold group.

One additional information: I use PRIS to set categories. Not sure, if it makes a difference.

 

Acceptance / Success Criteria

None

has to be finished together with

Lucidchart Diagrams

Activity

David Smith May 15, 2019 at 1:58 PM
Edited

merged to release-24.1.0

David Smith May 3, 2019 at 1:43 PM

Marcel Fuhrmann January 21, 2019 at 11:18 AM

Set severity to `major` since it is a regression.

Marcel Fuhrmann July 24, 2018 at 6:22 AM

I've just tested it manually (without using PRIS). So I remove a node from a threshold category, cleared the alarm and the alarm appeared again after some minutes.

Jeff Gehlbach May 18, 2018 at 2:50 PM
Edited

If this issue is reproducible, it represents a regression. Collectd should be listening for nodeCategoryMembershipChanged events (as well as others such as assetInfoChanged) and re-calculating the membership of the packages in threshd-configuration.xml when one of these is received.

Fixed

Details

Assignee

Reporter

Labels

Components

Sprint

Fix versions

Affects versions

Priority

Parent

PagerDuty

Created January 3, 2018 at 10:45 AM
Updated February 5, 2020 at 7:24 AM
Resolved February 5, 2020 at 7:24 AM

Flag notifications