Project

General

Profile

Actions
Copy link

Bug #3191

closed

Quality RRD inaccuracies and failure to update status in some circumstances

Added by Chris Buechler about 11 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Chris Buechler
Category:
Gateway Monitoring
Target version:
2.3
Start date:
09/09/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:

Description

There are some circumstances in which apinger puts in incorrect quality RRD data and fails to notice downtime. This needs some more specifics, but here are known examples of circumstances that fail.

1) use a monitor IP with 80% packet loss, with "Down" at the default 10, and it won't detect any packet loss and graphs no packet loss.
2) use a monitor IP with 80% packet loss, with "Down" at 30, and it'll take the gateway down appropriately but the RRD data will be wrong. Shows 100% loss much of the time.

There may be other specific circumstances that need to be added here.

This is true across all versions that have ever used apinger.

Actions
Copy link

Also available in: Atom PDF