Hmm, I'm trying a version of the info in the Admin Guide here: http://www.zenoss.com/community/docs/zenoss-guide/2.1.1/ch10s15.html#d0e3772

But it's not working...
For example, a user may want full-filesystem threshold events on /data to be critical. The following python script in the Threshold Transform of /Events/Perf/Filesystem:
if evt.component == '/data' and evt.severity != 0:
   evt.severity == 5

What I want to do, is take specific components and make the evt.severity to info ...

So I went to /Events/Perf/Filesystem, drop down arrow and More -> Transform and put in:
if evt.component == '/mnt/cleocdata5' and evt.severity != 0:
   evt.severity == 2
if evt.component == '/mnt/cleocmc7' and evt.severity != 0:
   evt.severity == 2
if evt.component == '/mnt/c3mcmc2' and evt.severity != 0:
   evt.severity == 2
if evt.component == '/mnt/cleocmc9' and evt.severity != 0:
   evt.severity == 2

For the components that I want set lower.... Nothing happens that I can see.

Should I instead map to a different class? Is this even a way to work around wanting a threshold per file system rather than per device in this instance?

--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University



James Pulver wrote:
I would guess that I could, however, map the events to /info or something based on the component name etc...?
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University



Anton Menshutin wrote:
No, templates are defined for devices/groups and not for components.

James Pulver wrote:
If I have a server with several file systems, and I don't want events at 90% full for some of them, but do for others - how would I do this by file system name? Can I?
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to