pcp
[Top] [All Lists]

Re: [pcp] Invalid proc.memory.vmhwn metric

To: Marko Myllynen <myllynen@xxxxxxxxxx>
Subject: Re: [pcp] Invalid proc.memory.vmhwn metric
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Sun, 15 May 2016 20:52:06 -0400 (EDT)
Cc: pcp developers <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5738B46F.3030803@xxxxxxxxxx>
References: <5738B46F.3030803@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: /YrZzPUFxNM2cvUtHu+Pe34QDxkOmg==
Thread-topic: Invalid proc.memory.vmhwn metric
Hi Marko,

----- Original Message -----
> Hi,
> 
> From http://man7.org/linux/man-pages/man5/proc.5.html:
> 
>   * VmHWM: Peak resident set size ("high water mark").
> 
> There's no proc.memory.vmhwm available as one would expect but
> proc.memory.vmhwn - and it turns out that the same typo is present
> everywhere in PCP sources so the value will always be zero.

Good catch.

> How should this be corrected? I could have sent a simple patch changing
> hwn->hwm everywhere

Yep, that's what's needed here.  (could you send that patch through?)

> but are there any backward compatibility
> restrictions that should be taken into account?

Noone can be validly using the "vmhwn" metric, so I vote to switch it
(correct error handling will kick in next release via 'unknown metric
name' return code).

We could write a pmlogrewrite(1) rule, but that seems like overkill in
this situation.

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>