This is a notification from the Help Desk.
On Nov 12, 2013 @ 05:32 pm, [email protected] wrote: Send smokeping-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of smokeping-users digest..." Today's Topics: 1. Re: Alerts for different slaves (Gregory Sloop) 2. Tuning smokeping for many hosts (Mirek Kalina) 3. Smokeping slave syslog (DeCamps, Miguel) ---------------------------------------------------------------------- Message: 1 Date: Tue, 16 Jul 2013 13:47:22 -0700 From: Gregory Sloop <[email protected]> Subject: Re: [smokeping-users] Alerts for different slaves To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii I keep forgetting to send to the list - Sorry Nick, you're going to get a duplicate! --- I think you'd have to build duplicate targets, and then assign one target to the master only, and the other target to the slave. [Where the target is the same device.] Then you'd assign different alert levels for the two targets. But I don't think there's a way to have two different alerts on the same target for different slave(s)/master(s). So, to get multiple separate alerts for the same device, you'll have to have the same device as two different targets. [And that will generate the ping or other check traffic again for each unique alert group...and also store an additional RRD file etc.] I'd guess that using Nagios to generate the alerts would probably be better. [Though the alerting condidtions nuance with Nagios isn't as sophisticated as in SP.] I use Nagios, not because I want multiple levels of thresholds, but because I want different alerts at different times, and destinations etc. Nagios has much more sophisticated alert/notification handling than SP. Perhaps someone else will have other suggestions, but that's the only way I can see to do it. -Greg --- NT> Hi, NT> Does anybody have any suggestions? NT> Thanks In Advance NT> Nick NT> On Fri Jul 12 18:02:17 2013, Nick Toseland wrote: >> Hi All, >> >> Is it possible to have alerts per slave? >> >> I have a slave that is approx 140ms from the master. >> >> If for instance I ping the www.bbc.co.uk from the master it is about 150 >> ms RTT, from the slave it is 12ms.. >> >> I would like an alert to fire if the RTT from the master goes above >> 200ms and an alert if the RTT from the slave goes about 40ms >> >> Many thanks >> >> Nick NT> _______________________________________________ NT> smokeping-users mailing list NT> [email protected] NT> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users -- Gregory Sloop, Principal: Sloop Network & Computer Consulting Voice: 503.251.0452 x82 EMail: [email protected] http://www.sloop.net --- ------------------------------ Message: 2 Date: Wed, 17 Jul 2013 09:09:44 +0200 From: Mirek Kalina <[email protected]> Subject: [smokeping-users] Tuning smokeping for many hosts To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Hi all, please is it possible not to use templates in RRDs::update() call in smokeping? I want to use rrdcached which is not allowed to use together with templated updates. I tried to comment out lines which defines template and it looks working well, but to tell the truth I don't know why it's used or what exactly templates do. Thanks a lot. Mirek ------------------------------ Message: 3 Date: Wed, 17 Jul 2013 13:47:40 +0000 From: "DeCamps, Miguel" <[email protected]> Subject: [smokeping-users] Smokeping slave syslog To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hello everyone! I am trying to integrate smokeping into my Open monitoring Distribution deployment as an alternative to IPSLA. Currently we have a Master slave configuration of Smokeping for a bunch of sensors we manage which works very well! The next stage of my project is to find out if there is a way for my slave instances running smokeping to report ALERTS into their own local syslog. I know that the Master Smokeping server reports the ALERT into its own syslog facility; but I need the alerts triggered to be reported on the Slave probes syslog so I can use the check_mk log watch agent of OMD to tie the alert to individual smokeping sensors that I monitor using Check_mk. Please help! Thank you! Sincerely, Miguel DeCamps Data Engineer Tel: 212.849.2340 | Cell: 917.596.2636 | 24hr Support 888.543.2000 www.mcgrawcom.net<http://www.mcgrawcom.net/> Take a loot at our e-brochure: http://www.mcgrawcom.net/ebrochure Check out our e-brochure to see how we are redefining Hosted VoIP with InPacket, McGraw's Unified Communications Platform! http://www.mcgrawcom.net/inpacket/demo/ [Description: Description: cid:[email protected]] [Description: Description: bcmccna] [Description: Description: Description: cid:[email protected]] <http://www.linkedin.com/company/mcgraw-communications> This email and the attached documents are provided by McGraw Communications solely for your review. This email and the attached documents are confidential and are the property of McGraw Communications. This email is not to be forwarded, copied or otherwise disseminated without the express written consent of McGraw Communications. Any Proposal contained in this e-mail is provided by McGraw Communications solely for your review. This proposal is confidential and is the property of McGraw Communications and shall not be copied or otherwise disseminated without the express written consent of McGraw Communications -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130717/79f5dbe5/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 16356 bytes Desc: image001.gif Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130717/79f5dbe5/attachment.gif -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 1860 bytes Desc: image002.jpg Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130717/79f5dbe5/attachment.jpg -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.jpg Type: image/jpeg Size: 986 bytes Desc: image003.jpg Url : http://lists.oetiker.ch/pipermail/smokeping-users/attachments/20130717/79f5dbe5/attachment-0001.jpg ------------------------------ _______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users End of smokeping-users Digest, Vol 77, Issue 6 ********************************************** ------ This is an automated response. Your issue has been noted. We'll be in touch soon. Please reply to this email or visit the URL below with any additional details. http://florin-pc/portal/view-help-request/36
_______________________________________________ smokeping-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
