| To: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
|---|---|
| Subject: | Re: automatic derived metrics slowing down remote pcp clients, esp. pmlogconf |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Sat, 14 May 2016 18:08:52 -0400 |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <d2f3f657-fe0b-c967-b7c0-e4603c9f5f9c@xxxxxxxxxx> |
| References: | <20160514193945.GC1418@xxxxxxxxxx> <d2f3f657-fe0b-c967-b7c0-e4603c9f5f9c@xxxxxxxxxx> |
| User-agent: | Mutt/1.4.2.2i |
Hi - > since derived metrics are never logged (they're defined client side only), > the above makes the most sense. This is akin to the call to the call to > __pmSetInternalState(PM_STATE_PMCS) in tools such as pmlogextract and other > places. Looks like there are few othertools that need to set this too. OK, how about: diff --git a/src/pmlogconf/pmlogconf.sh b/src/pmlogconf/pmlogconf.sh index 3531c676130e..dfd2e92137f4 100755 --- a/src/pmlogconf/pmlogconf.sh +++ b/src/pmlogconf/pmlogconf.sh @@ -28,6 +28,11 @@ # Get standard environment . $PCP_DIR/etc/pcp.env +# Clear this part to ensure many short-lived pmprobe children +# don't waste time analyzing derived metrics. +PCP_DERIVED_CONFIG= +export PCP_DERIVED_CONFIG + status=1 tmp=`mktemp -d /tmp/pcp.XXXXXXXXX` || exit 1 trap "rm -rf $tmp; exit \$status" 0 1 2 3 15 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: automatic derived metrics slowing down remote pcp clients, esp. pmlogconf, Mark Goodwin |
|---|---|
| Next by Date: | Re: automatic derived metrics slowing down remote pcp clients, esp. pmlogconf, Mark Goodwin |
| Previous by Thread: | Re: automatic derived metrics slowing down remote pcp clients, esp. pmlogconf, Mark Goodwin |
| Next by Thread: | Re: automatic derived metrics slowing down remote pcp clients, esp. pmlogconf, Mark Goodwin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |