Project

General

Profile

Actions
Copy link

Todo #5645

closed

dpinger needs gateway identification in logs

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

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Gateway Monitoring
Target version:
2.3
Start date:
12/15/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:

Description

dpinger's logs currently have no identification of which gateway or which process they came from. The log output needs to contain something identifying the gateway.

Maybe the best way to do it would be adding a command argument for an identifier that it inserts into all its log messages. eg "dpinger ... -x GW_WAN ..." would include GW_WAN in all log output (replacing 'x' with whatever's available and makes sense).

As is, it can be difficult to troubleshoot multi-WAN and dual stack single WAN environments.

Actions
Copy link

Also available in: Atom PDF