6/12/2023 0 Comments Pingplotter set alert![]() Set Samples to examine to 10000 (or some other high number). As long as things are good on the network, this event will fire each time a sample is collected. period - and notify on a lower packet loss percentage. This is the exact opposite of the first notification type above. In previous versions, this was the only supported notification type. This means the event will happen over and over again – on each sample that causes the alert to fire. The event will happen each time the conditions are met. One use of this is to have PingPlotter email you each time conditions go bad (see above), and then when they improve again – but not to tell you anything in between. As soon as the conditions move from bad to good (based on your settings), then this event will happen. ![]() This happens when network conditions improve so that the alert is no longer firing. When alert conditions end (leaves alert state) As soon as the alert stops happening, then as soon as it starts again, this event will happen again. This is a popular use – as you find out about new conditions when they happen, but don't have to be bothered again. Click the filter icon to create a subnet mask, the pencil & paper icon to edit the alert, or the red X to remove the alert from either Your Alert Library or. As long as the conditions continue, though, the event won't be repeated. The first time alert conditions occur, the event will happen. When alert conditions start (enters alert state) Note that any alert can have multiple events of the same type, so you can set up a single alert to do something at any one or all of these times. Many of the events share a notification mechanism.
0 Comments
Leave a Reply. |