feldman wrote:
> Ok, this what I have done:
>
> 1/ set min max treshold launch a perf/filesytem event : works
> 2/In perf/filesystem class, add an EventClass Mappings called size
> 3/edit this mapping : EventClassKey=size, transform=evt.summary =
> evt.message.split()[6]
> 4/In the event manager/ Commands, create the following command :
> toto True 1 1 echo ${evt/summary} >/test
> (eventClass = '/Perf/Filesystem')
>
> What happens is that an event is triggered but I can not see anything into
> the test file.
>
> I don't knwo what is wrong with this. In the event command, what does the /
> directory refers to (maybe is it the mystake...)
>
>
> Thanks for your help
The /test in your event command would try to create the file 'test' in / on the
filesystem.
The zenoss user will most likely not have permission to write to /, so if you
try to do
Code:
/bin/echo ${evt/summary} > /tmp/test
the file should appear in /tmp
Also, testing only on the /Perf/Filesystem Event Class can possibly trigger the
command on other Filesystem related events. If this is a specific case (with
the file size) then it might be worth creating an Event Class that only exists
for this specific case to avoid other events arriving in there. Alternatively
you could add a rule in the Event Command to only fire the command for a
specific Device, etc
HTH,
Jay
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=30600#30600
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
