pcp
[Top] [All Lists]

[Bug 1337102] New: pmlogger should avoid redundant logging

To: pcp@xxxxxxxxxxx
Subject: [Bug 1337102] New: pmlogger should avoid redundant logging
From: bugzilla@xxxxxxxxxx
Date: Wed, 18 May 2016 10:02:39 +0000
Auto-submitted: auto-generated
Delivered-to: pcp@xxxxxxxxxxx
https://bugzilla.redhat.com/show_bug.cgi?id=1337102

            Bug ID: 1337102
           Summary: pmlogger should avoid redundant logging
           Product: Fedora
           Version: 24
         Component: pcp
          Assignee: nathans@xxxxxxxxxx
          Reporter: myllynen@xxxxxxxxxx
        QA Contact: extras-qa@xxxxxxxxxxxxxxxxx
                CC: brolley@xxxxxxxxxx, fche@xxxxxxxxxx, lberk@xxxxxxxxxx,
                    mgoodwin@xxxxxxxxxx, nathans@xxxxxxxxxx,
                    pcp@xxxxxxxxxxx, scox@xxxxxxxxxx



Description of problem:
When doing something like this after starting the pmlogger service using the
default configuration:

echo "log mandatory on 10sec kernel.all.load" | pmlc -P
echo "log mandatory on 10min kernel.all.load" | pmlc -P

pmlogger logs these logging changes in its logs (rightly so). However, if doing
the latter several times in a row (for example for a script) pmlogger would
still log the current state even if there was no change at all in logging
configuration making the log messages redundant.

The issue with these redundant log messages is that they make it much harder to
spot the actual changes from the log file and of course eat quite a lot of disk
space in the long run.

While one could use "query" to determine the current status and then call pmlc
only if needed. But parsing pmlc output and adding logic whether or not to call
pmlc doesn't sound optimal in this case and doesn't guarantee that all calls to
pmlc are done after such checks.

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=DQ0S5xxfss&a=cc_unsubscribe
<Prev in Thread] Current Thread [Next in Thread>