Actions
Todo #5645
closed
dpinger needs gateway identification in logs
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.
Updated by Jim Thompson about 9 years ago
need to do this semi-automatically, or we'll eventually screw it up.
Updated by Renato Botelho about 9 years ago
- Status changed from New to Feedback
Available in dpinger 1.1
Updated by Chris Buechler almost 9 years ago
- Status changed from Feedback to Resolved
this is all fine now
Actions