Project

General

Profile

Actions

Bug #13969

closed

Status_Monitoring ignores NAT states

Added by Jim Pingle about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Status_Monitoring
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

The fix for #13966 corrected parsing of NAT states for RRD, but the Status_Monitoring frontend appears to be ignoring NAT states.

In rrd_fetch_json.php it is set to ignore.

If I set a description the field appears to work OK. There isn't any indication of why it was ignored in the Git history but given that the data has been bad for a while, that may be why.

Easy enough to correct now that the data should be collected properly, though.

To me, I have a fix pending.

Actions #1

Updated by Jim Pingle about 1 year ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Fix pushed, will be in dev snapshots.

Not picked to 23.01 since it doesn't make sense to update this without having the other patch in place.

Actions #2

Updated by Jim Pingle about 1 year ago

To apply the fix manually in the meantime, use this patch:

diff --git a/blah/usr/local/www/rrd_fetch_json.php b/blah/usr/local/www/rrd_fetch_json.php
index df0401f96e89..4d7574819ac9 100644
--- a/blah/usr/local/www/rrd_fetch_json.php
+++ b/blah/usr/local/www/rrd_fetch_json.php
@@ -226,7 +226,8 @@ foreach ($side as $settings) {
                                $ds = "state changes";
                                break;
                        case "pfnat":
-                               $ignore = true;
+                               $unit_acronym = "";
+                               $ds = "NAT states";
                                break;
                        case "inpass":
                                $ninetyfifth = true;
Actions #3

Updated by Azamat Khakimyanov about 1 year ago

  • Status changed from Feedback to Resolved

Tested on 23.05-DEV (built on Fri Apr 07 01:20:44 UTC 2023) and on 2.7-DEV (built on Wed Apr 12 06:05:24 UTC 2023)

Status/Monitoring now shows NAT states as a one of the options of 'System: States' and 'NAT states' counter evaluates according to amount of active states.

I marked this Bug as resolved.

Actions

Also available in: Atom PDF