allow categories when creating downtime schedules

Description

It would be nice to have the abillity to select nodes by their surveillance category so that any node that was part of "Site A" would be added to the downtime roster when "Site A" was going down... This could also be "All Oracle 9 servers" or "All Novell 5.x Servers" depending on how you have your surveillance categories defined. It would be doubly nice if you could first select a category, then select nodes within that category or all nodes in category. This should be limited only to the amount of categories you have defined. Each time you select a category and are done adding nodes from that category, a new category select option would appear so that the previous category selection is still visible.

Environment

Operating System: All Platform: All

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Marcel Fuhrmann May 14, 2018 at 8:16 PM

Still a very important topic. It is very hard to add a lot of nodes into schedules outage config.

I usually don't have time and motivation to add every single node... Even when I get alarms in case of scheduled outages.

Ron Roskens October 8, 2013 at 1:04 PM

I added a couple of enhancements to the Scheduled Outages page that should make things a little bit easier when selecting nodes.

In the nodelabel search box, you can now prefix the search string with a couple of special symbols to alter the search behavior:

'@' will let you search for surveillance categories
'#' Will search for nodes who are in the specified surveillance category
'$' will let you search for requisition names
'%' will search for nodes in a requisition that starts with the search string.

There was a suggestion to use a visualsearch javascript enhancement to the search box. (http://documentcloud.github.io/visualsearch/), instead of using special characters sequences.

I think a good second step would be working out a better method for getting the list of categories or requisition names. Creating the lists based on the values obtained from the nodes returned via getAllNodes() seems to be a waste of cpu/memory.

Ron Roskens October 8, 2013 at 12:57 PM

also appears to be a duplicate of this issue.

Jan Lukes [X] May 23, 2013 at 7:51 PM

OpenNMS Support ticket #2286. Adding my vote. Thanks.

Jan Lukes
Sophos Inc.

Seth Leger (community account) August 10, 2010 at 4:28 PM

  •  

    •  

      • has been marked as a duplicate of this bug. ***

Details

Assignee

Reporter

Components

Affects versions

Priority

PagerDuty

Created November 22, 2007 at 8:42 PM
Updated September 21, 2021 at 9:17 PM