![]() Also, the graphs look a little bit neater and easier to read. This reduces duplicate emails and maintains accuracy. Then it has to check for another step (another 5 minutes) before sending an alarm email again. We get the accuracy, and we can also set up alarms that say ‘in the last three steps (15 minutes) if there is 15% or higher loss in two of them, then alarm. So I went back to 5 minute steps (300 seconds) with 290 pings (so it’s still very accurate as it’s almost always pinging every second). I could only mostly get that to work but its annoying getting 10 emails about the same issue as each additional step with loss after 6, that is within 15 minutes also will send an alarm. Well, there may be a way, but I wasn’t able to figure it out. You can’t say in 45 steps (15 minutes = 900 seconds, 900seconds/20secondsteps=45steps) if there is 20% loss or greater on just 6 of them, then alarm, then stop alarming until another 15 minutes of checking occurs. However, having very short step times makes it hard to work with the email alarms. *To match pingplotter in statistics, I’ve set /etc/smokeping/config.d/Probes to be pings 9, step 10, and timeout 1Īfter a lot of testing I got the detailed graphs to work well. Multiple conditions for alerts can also be set up. The alerts could be more strict or less strict. For example, the circuit drops greater than 20% packets for five intervals in a row(in this example there are 10 seconds), an email could be sent out to alert us. It should also be set up to email alerts if behavior conditions are met. High ping times (indicated in gray and black) may indicate high percentage of bandwidth usage. It can be used to identify if the circuit is responsible for a dropped phone call or a page timeout at a specific time of day, should a customer inquire about that. This is very useful for intermittent or short problems. To set up smokeping for in-depth monitoring of circuits similar to mytraceroute and pingplotter so that we can obtain a precision visual representation of circuit behavior. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |