ZenPacks : EmailPing - Monitor your Email-based Alerting Mechanism : Comments

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Fri, 23 Apr 2010 05:20:14 GMT

hi, i use this zenpack and it works well.

it's possible to use it as a check on differend device?

i've several antispam device and it's very usefoul to check if antispam workflow is working correctly....

but with this zenpack i can check only one email account...

it possible to add more mail account and have different alert depending on mail accont that have issue?

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Fri, 23 Apr 2010 14:51:49 GMT

That was going to be my next incarnation for this ZenPack. I can't believe you picked up on it that fast.

The following will work, however, it will break the performance graphs:

Make a copy of emailping.py, naming it emailping1.py
On line 101 of emailping1.py, change self.name = 'emailping' to 'emailping1'
Make a copy of ZenPack.../daemons/emailping to emailping1
Create a soft link in $ZENHOME/bin called emailping1 that points to ZenPack.../daemons/emailping1
You should now be able to see emailping1 listed on the Daemons page. Just configure it and start it like you did with the first one.

One caveat is that Zenoss uses the class name for the log file, so all the daemons will be dumping into the same emailping.log file.

If you do this, know that the component field of an event is populated with the following information:

epSendFailure - component = toaddress

epPopConnectionFailure - component = pophost
epPopReceiveFailure - component = popaccount. If popusername takes the form aaa@bbb.ccc, then popaccount = popusername. If popusername is just a name, then popaccount = popusername@pophost
epAccountReceiveFailure - toaddress

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Sun, 25 Apr 2010 06:07:46 GMT

for multi smpt server config i found a document based on nagios check_email_delivery that allow to use various parameter

http://community.zenoss.org/docs/DOC-2515

maybe a mix of this check and your zenpack based on device and not on daemons would be perfect

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Wed, 12 Jan 2011 23:20:53 GMT

This is a great tool covering several checks with one pack. Any idea how you would create an alert based on the perf emailping queue size or perf round trip time?

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Thu, 13 Jan 2011 02:32:10 GMT

I didn't build those into the daemon, but you could create thresholds on the data sources and generate alerts from that. Note that I've got the latest version 1.1.0 waiting to be published. Also, each time the daemon starts it add/removes data sources from the performance template based on changes to the configuration file. So if you change a toaddress, you would need to recreate the thresholds.

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Wed, 19 Oct 2011 08:46:18 GMT

I uninstall this ZenPack, and "localhost emailping heartbeat failure" stay to alert me. I tried find configuration in zenoss directory, but without success. How I can solve this?

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Thu, 08 Dec 2011 18:20:09 GMT

When i tried to install this zenpack an error occured... permision denied...

I checked some files to see if the owner was zenoss:zenoss...

and the error was the same...

so...

I added the user zenoss to the sudoers... at /etc/sudoers and everything ran without problems...

Hope this help

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Wed, 04 Jan 2012 21:12:46 GMT

Excellent ZenPack. I am just having 1 issue. I am getting negative transit times, which appears to be coming about as the timestamp in the outgoing email subject is in PST. Is there a way of getting this time stamp to use my current time zone GMT?

thanks

Glen

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Mon, 06 Feb 2012 09:52:06 GMT

UPDATE: Ignore this - I accidentally editted the "monitor" setting to be "gmail" instead of "localhost".

I'm on version 3.2.1 and I'm getting the following errors:

2012-02-06 09:34:21,793 INFO zen.EmailPing: Connecting to localhost:8789

2012-02-06 09:34:21,806 INFO zen.EmailPing: Connected to ZenHub

2012-02-06 09:34:21,918 ERROR zen.EmailPing: Could not retrieve service EventService

2012-02-06 09:34:21,918 CRITICAL zen.EmailPing: Invalid monitor: gmail

2012-02-06 09:34:21,919 INFO zen.EmailPing: Deleting PID file /usr/local/zenoss/zenoss/var/emailping-gmail.pid ...

2012-02-06 09:34:21,919 INFO zen.EmailPing: Daemon EmailPing shutting down

I don't have any collectors set up - it should all be localhost.

Any help appreciated!

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Fri, 25 May 2012 17:50:58 GMT

A little more help on how to create thresholds on the data sources?

These graphs show up on my localhost collector unlike all my other graphs which show up attached to devices.

I would be fine with attaching it to the device I use to monitor my mailserver but I can't find the data sources you refer to?

Sorry I've only been messing with Zenoss for a couple of weeks.

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Mon, 23 Jul 2012 16:44:27 GMT

Hi - any ideas on how to pull the graphs created from this zenpack into a graph report in the reports section?

RE: EmailPing - Monitor your Email-based Alerting Mechanism

community@zenoss.org — Wed, 09 Oct 2013 13:21:44 GMT

Has anyone tried this on Core 4.2.3 yet. I have upgraded from 3.2.1 to 4.2.3 and now I get the following errors when I try and start the Daemon

DEBUG zen.GlobalConfig: Unknown option: --zodb-admin-user

DEBUG zen.GlobalConfig: Unknown option: --zodb-admin-password

DEBUG zen.GlobalConfig: Unknown option: --amqphost

DEBUG zen.GlobalConfig: Unknown option: --amqpport

DEBUG zen.GlobalConfig: Unknown option: --amqpvhost

DEBUG zen.GlobalConfig: Unknown option: --amqpuser

DEBUG zen.GlobalConfig: Unknown option: --amqppassword

DEBUG zen.GlobalConfig: Unknown option: --amqpusessl

DEBUG zen.GlobalConfig: Unknown option: --amqpadminport

DEBUG zen.GlobalConfig: Unknown option: --amqpadminusessl

DEBUG zen.GlobalConfig: Unknown option: --zep-db-type

DEBUG zen.GlobalConfig: Unknown option: --zep-host

DEBUG zen.GlobalConfig: Unknown option: --zep-port

DEBUG zen.GlobalConfig: Unknown option: --zep-db

DEBUG zen.GlobalConfig: Unknown option: --zep-user

DEBUG zen.GlobalConfig: Unknown option: --zep-password

DEBUG zen.GlobalConfig: Unknown option: --zep-admin-user

DEBUG zen.GlobalConfig: Unknown option: --zep-admin-password

DEBUG zen.GlobalConfig: Unknown option: --zep-uri

DEBUG zen.GlobalConfig: Unknown option: --zodb-db-type

Any help would be appreciated