Ticket #1716 (closed enhancement: fixed)

Opened 17 months ago

Last modified 6 weeks ago

Allow "begins with" and "does not begins with" criteria for Device Class in alert rules

Reported by: jstevens Owned by: ecn
Priority: 1 - Blocker Milestone: zenoss-2.1
Component: All Version: 2.0.0
Severity: low Keywords:
Cc: Documentation: Not required
Installer: Reviewed: yes

Description

Right now if you specify Device class is /Server in an alert rule it doesn't match subclasses such as /Server/Linux. It would be useful (and also get rid of some user confusion) if we also provided items in the "is/is not" dropdown for "starts with" and "doesn't start with" or something like that. This effectively lets people match a device class and all subclasses.

Change History

Changed 15 months ago by edahl

  • priority changed from high to blocker

Changed 14 months ago by jstevens

  • owner changed from jstevens to ecn

Changed 14 months ago by ecn

  • status changed from new to closed
  • resolution set to fixed

(In [6910]) * fixes #1716: add "begins with" and "does not begin with" to the event filter for EventClass comparisons

Changed 14 months ago by ecn

(In [6912]) * fixes #1716: (remove silly pdb statement)

Changed 14 months ago by ecn

(In [6915]) * fixes #1716: DeviceClasses are like EventClasses

Changed 6 weeks ago by bbibeault

  • documentation set to Not required
  • reviewed set
Note: See TracTickets for help on using tickets.