Needing new command line option

Riku Meskanen riku.h.meskanen at jyu.fi
Mon Oct 22 15:56:17 UTC 2012


Hello,

On 22 Oct 2012, at 17:54, Jiri Popelka <jpopelka at redhat.com> wrote:

> We add the LOG_PID option to openlog() call
> so there's PID included with each message.

That's definitely better than nothing, solves
strictly speaking the local debugging need
quite nicely.

But I don't see how it solves the need to be
able to match logged lines at remote log
analyser (like splunk). over the longer period
of time and over multiple restarts (pid changes),
match each service daemon logs just to that 
service?

You may think that, ha, we do the differentiating
with IP prefixes until you realise that with MPLS
you can reuse same IP addresses over and over
again in separate VRF/RD instances. This happens
a lot with service providers networks as they connect
different customers each using same private addresses 
again and again to build their customers networks.
I don't know how often though dhcp is needed there,
that's usually on customers own servers.

You could use server name and IP addresses
used together (combined key), but then need to track 
what prefixes are configured at each server still needs 
to be updated at log analyser each time you change things. 
With tags no need for that. Logged lines still are
kept with ease together as there is unique identifier
that remains the same.

LOG_PID good, syslog facilities good as they
last, but IMHO something that remains same
and scales well even better. 

The proposal patch does not change anything
to current practise by default no tag. Only
if it's given on command line then it will appear. 

I have strong reason to assume that it doesn't break 
anything especially if you don't use it. And you use 
it only if you really need it :)

:-) riku

-- 
	[ This .signature intentionally left blank ]



More information about the dhcp-hackers mailing list