Can someone provide a valid reason for mucking with event summary text every other release? (I searched the forums for an answer to this, and this thread was the closest I could find.) I just upgraded to 2.3.2, and have noticed that many of my event transforms have quit working as well; mainly any transform that depended on the summary text "snmp trap TRAPTYPE". A few releases ago it was "snmp trap TRAPTYPE from deviceName", and I had to fix them all back then as well. I have a feeling the "correct" way to do this is actually to differentiate on the SNMP OID (snmpTrapOID?) which is what I guess I'll be switching to in the future. Is this how others are mapping SNMP traps to events? Since I have to redo so many of my transforms, I figured I'd ask what the "best practice" is now.
Just thought I'd throw in my two cents (and thanks in advance). --seth P.S. Other than that, the only other issue I had with the upgrade is just an annoyance dealing with various Services being set as monitor=true after every upgrade, when I had explicitly set them to monitor=false before. Luckily I wrote down the Services set to monitor=true before the upgrade, so I could reset the monitor values immediately afterwards. I ended up having to set monitor=false on 22 WinServices and 3 Registered IPServices after the upgrade. I'll probably end up submitting a ticket for this. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=29965#29965 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
