Wiki : Transforms based on time : Comments

RE: Transforms based on time

community@zenoss.org — Mon, 22 Mar 2010 15:57:52 GMT

Thanks for this - it's useful.

RE: Transforms based on time

community@zenoss.org — Mon, 22 Mar 2010 16:10:45 GMT

Glad that you found it useful.

RE: Transforms based on time

community@zenoss.org — Wed, 28 Jul 2010 18:16:40 GMT

Hey Ryan,

I've been happily making transforms based on minutes and hours, but I can't seem to get anything using the current day working. It's really strange - does it definitely work for you?

I tried a transform with: -

if (time.localtime()[2] in [0, 1, 2, 3, 4, 5, 6]):

evt.TransformNote="This worked"

... but this doesn't work. The same with localtime()[3] does, so I'm confused.

RE: Transforms based on time

community@zenoss.org — Wed, 28 Jul 2010 18:53:03 GMT

You're definitely doing something wrong man. I think you're not understanding the way the numbers work or something...

>>> time.localtime()[3]
14
>>> time.localtime()[2]
28
>>> if (time.localtime()[3] in [0, 1, 2, 3, 4, 5, 6, 14]):
... print 'bleh'
...
bleh
>>> if (time.localtime()[2] in [0, 1, 2, 3, 4, 5, 6, 28]):
... print 'bleh'
...
bleh

RE: Transforms based on time

community@zenoss.org — Wed, 28 Jul 2010 18:54:27 GMT

if (time.localtime()[2] in [0, 1, 2, 3, 4, 5, 6]): will only trigger on the 1st, 2nd, 3rd, 4th, 5th, and 6th day of each month. It literally represents the current day. For instance, today is the 28th.

RE: Transforms based on time

community@zenoss.org — Wed, 28 Jul 2010 22:17:19 GMT

Thanks so much for this response - I was taking it to mean 'day of week'!! What an idiot.

It looks like I may be able to use time.localtime()[6]? I'll try it tomorrow.

Cheers again.

RE: Transforms based on time

community@zenoss.org — Wed, 28 Jul 2010 23:40:03 GMT

Yes, time.localtime()[6] is what you want... I don't quite understand it though since every reference I've found to it says that 0 should represent monday and 6 should represent Sunday, yet we are clearly Wednesday today and every time I try it on any of my servers or my workstation (which all have the correct date/time, I get the following results:

rmatte@noc:~$ date
Wed Jul 28 19:30:14 EDT 2010

>>> time.localtime()
time.struct_time(tm_year=2010, tm_mon=7, tm_mday=28, tm_hour=19, tm_min=30, tm_sec=26, tm_wday=2, tm_yday=209, tm_isdst=1)

So 2 is Wednesday then? It's a bit weird.

RE: Transforms based on time

community@zenoss.org — Wed, 28 Jul 2010 23:41:08 GMT

Oh nevermind, I wasn't thinking of it right... here's the correct index...

0: Monday

1: Tuesday

2: Wednesday

3: Thursday

4: Friday

5: Saturday

6: Sunday

That makes sense.

RE: Transforms based on time

community@zenoss.org — Thu, 26 Sep 2013 13:01:13 GMT

This a great bit a code. Would there be a way to make it look at a certain device class and event class and then only change the severity of the event. We would like to see the event in the dashboard, but we don't want to alert on it during a certain period of time.

RE: Transforms based on time

community@zenoss.org — Thu, 26 Sep 2013 13:41:25 GMT

It's simple to do stuff like that. Search the community site for "example transforms" and you'll find lots of examples of how to do that. When you double click on an event and expand the details sections that pop up on the right you'll see all of the different properties that you can access in an event transform.

You could just add something to the transform like:

if evt.DeviceClass == "/My/Device/Class" and evt.eventClass == "/My/Event/Class":

evt.severity = 5

Severities, 5 = Critical, 4 = Error, 3 = Warning and so on...

RE: Transforms based on time

community@zenoss.org — Thu, 26 Sep 2013 15:51:46 GMT

thanks for the super fast response. I was thinking about this a bit more and thought maybe it would be best to use maintenance windows to control this rather than a time frame in the transform for the managebility and visibility. Below are somethings that have tried.

This one is based on time and it works fine.

import time, re
if re.match('/Perf/CPU', evt.eventClass):
if re.match('/Server/Windows/WMI/MSSQLServer/Cluster', evt.DeviceClass):
if time.localtime()[3] >= 10 and time.localtime()[3] < 11:
evt.severity = 3

This one is based on productions state but doesn't seem to be working just yet.

import time, re
if re.match('/Perf/CPU', evt.eventClass):
if re.match('/Server/Windows/WMI/MSSQLServer/Cluster', evt.DeviceClass):
if re.match('Maintenance',evt.prodState):
evt.severity = 3

Also tried this

import time, re
if re.match('/Perf/CPU', evt.eventClass):
if re.match('/Server/Windows/WMI/MSSQLServer/Cluster', evt.DeviceClass):
if evt.prodState == Mainteancne:
evt.severity = 3

I also tried replacing maintenance with 300 for the conversion.

Any ideas on the one for production state would be greatly appreciated.

RE: Transforms based on time

community@zenoss.org — Thu, 26 Sep 2013 15:59:16 GMT

For evt.prodState you need to use an integer value, not a string. You can see the production state to integer conversions under Advanced -> Settings. For instance, Production would be 1000, Maintenance would be 300. Don't use re.match for doing straight matches, it's much more intensive on the system to process it. If you're not specifically using regex statements then you should just be using ==.

End result would be...

import time

if evt.eventClass == '/Perf/CPU' and evt.DeviceClass == '/Server/Windows/WMI/MSSQLServer/Cluster' and evt.prodState == 300:

evt.severity = 3

RE: Transforms based on time

community@zenoss.org — Thu, 26 Sep 2013 16:06:15 GMT

Works perfectly, thanks for the tips.