I think I found 4 solutions but am unsure as to which way to go: 1. Do not send alerts to users at the "warning" level. 2. Hack $ZENHOME/Products/ZenRRD/zencommand.py line 504 to suppress the cmd.command portion. 3. Hack $ZENHOME/Products/ZenRRD/zencommand.py line 505 to log at a debug level instead. 4. Run Away !
Your thoughts ? -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of James Pulver Sent: Thursday, May 14, 2009 11:41 AM To: General discussion of using Zenoss Subject: Re: [zenoss-users] visability of admin credentials in alerts See: http://forums.zenoss.com/viewtopic.php?t=6721&highlight=credentials+alerts http://forums.zenoss.com/viewtopic.php?t=6379&highlight=credentials+alerts Searching the forums for "credentials alerts" found this. -- James Pulver Information Technology Area Supervisor LEPP Computer Group Cornell University Chris Gregors wrote, On 5/14/2009 1:33 PM: > I just noticed that some alerts are exposing the monitoring credentials to > the alert receiver. An example alert: > ------------------------- > Device: hostname.example.com > Component: > Severity: Warning > Time: 2009/05/14 09:09:52.000 > Message: > Command timed out on device hostname.example.com: > $ZENHOME/Products/WMIPerformanceMonitor/libexec/wmi_stats.pl TS " > hostname.example.com " "10.20.30.40" "domain\user" "userpassword" > Event Detail > Acknowledge > Delete > Device Events > ------------------------- > > Where is this coming from ? > > > _______________________________________________ > 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
